Triple
T37608336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roh |
E935715
|
entity |
| Predicate | hasTypeOfAncestry |
P116143
|
FINISHED |
| Object | eponymous ancestry |
—
|
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: eponymous ancestry | Statement: [Roh, hasTypeOfAncestry, eponymous ancestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfAncestry Context triple: [Roh, hasTypeOfAncestry, eponymous ancestry]
-
A.
hasAncestralType
Indicates that one type is derived from, or originates from, another more primitive or original type in an inheritance or lineage hierarchy.
-
B.
alsoHasAncestry
Indicates that an entity possesses an additional ancestral lineage or heritage beyond its primary recorded ancestry.
-
C.
typeOfAncestor
Indicates that one entity is an ancestor (of any generational distance) of another entity.
-
D.
typeOfAncestry
chosen
Indicates that one entity’s ancestry or lineage is characterized as being of a particular type or origin in relation to another entity.
-
E.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:18 p.m.