Triple
T29375534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaparoan languages |
E744983
|
entity |
| Predicate | notProvenGeneticRelation |
P8167
|
FINISHED |
| Object | Quechuan languages |
—
|
NE NERFINISHED |
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: Quechuan languages | Statement: [Zaparoan languages, notProvenGeneticRelation, Quechuan languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notProvenGeneticRelation Context triple: [Zaparoan languages, notProvenGeneticRelation, Quechuan languages]
-
A.
notGeneticallyRelatedTo
chosen
Indicates that there is no genetic or hereditary relationship between the two entities.
-
B.
proposesGeneticRelationshipBetween
Indicates that one entity puts forward or suggests the existence of a genetic relationship between two or more entities.
-
C.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
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.
notMotherOf
Indicates that the subject is explicitly not the mother (biological, adoptive, or recognized maternal parent) of the object.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669adca6c81909efccc10634f9a63 |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:30 p.m.