Triple
T34121911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lom people |
E875160
|
entity |
| Predicate | sharesAncestralLinksWith |
P18399
|
FINISHED |
| Object | Dom people |
—
|
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: Dom people | Statement: [Lom people, sharesAncestralLinksWith, Dom people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesAncestralLinksWith Context triple: [Lom people, sharesAncestralLinksWith, Dom people]
-
A.
ancestralLinks
Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
-
B.
sharesCommonAncestorWith
chosen
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
C.
sharesFamilyLineageWith
Indicates that two entities descend from the same family line or share common ancestors.
-
D.
hasHeritageConnectionWith
Indicates a relationship where two entities are linked through shared, inherited, or culturally transmitted heritage or ancestry.
-
E.
sharesDNAWithHumans
Indicates that one entity possesses genetic material that is evolutionarily related to, and partially identical with, that of humans.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
Created at: May 1, 2026, 1:53 a.m.