Triple
T23278851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pamona |
E588798
|
entity |
| Predicate | hasAncestralTo |
P151648
|
FINISHED |
| Object | younger generations of Pamona people |
—
|
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: younger generations of Pamona people | Statement: [Pamona, hasAncestralTo, younger generations of Pamona people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralTo Context triple: [Pamona, hasAncestralTo, younger generations of Pamona people]
-
A.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
B.
hasAncestralType
Indicates that one type is derived from, or originates from, another more primitive or original type in an inheritance or lineage hierarchy.
-
C.
destinedAncestorOf
Indicates that one entity is fated or preordained to become an ancestor of another entity in the future.
-
D.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
E.
hasAncestralEvent
Indicates that an entity is associated with a past ancestral occurrence or event in its lineage.
- F. None of above. chosen
Provenance (4 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957991108190ac82fa6dd355f722 |
completed | April 29, 2026, 5:22 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:49 p.m.