Triple
T17378313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onge people |
E422498
|
entity |
| Predicate | geneticHeritage |
P87422
|
FINISHED |
| Object | distinct from mainland Indian populations |
—
|
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: distinct from mainland Indian populations | Statement: [Onge people, geneticHeritage, distinct from mainland Indian populations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticHeritage Context triple: [Onge people, geneticHeritage, distinct from mainland Indian populations]
-
A.
geneticOrigin
chosen
Indicates that one entity is the source or contributor of another entity’s genetic material or hereditary traits.
-
B.
countryOfHeritage
Indicates the country from which an entity’s cultural, ancestral, or familial heritage originates.
-
C.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
D.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
E.
ancestralSubgroups
Indicates that one group consists of or descends from earlier, foundational subgroups within a lineage or hierarchy.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6ea56c8190b56d966ccf2c91f7 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.