Triple
T7430412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonsea language |
E171473
|
entity |
| Predicate | isGeneticallyRelatedTo |
P72989
|
FINISHED |
| Object | Tondano language |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Tondano language | Statement: [Tonsea language, isGeneticallyRelatedTo, Tondano language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeneticallyRelatedTo Context triple: [Tonsea language, isGeneticallyRelatedTo, Tondano language]
-
A.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
B.
notGeneticallyRelatedTo
Indicates that there is no genetic or hereditary relationship between the two entities.
-
C.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
E.
hasGeneticAffiliation
chosen
Indicates that one entity is genetically related or affiliated with another, such as sharing ancestry, lineage, or genetic characteristics.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f32324c481908c9ba594e8456728 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.