Triple
T13017190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaeus |
E322582
|
entity |
| Predicate | typeOfAncestralFigure |
P95710
|
FINISHED |
| Object | tribal ancestor |
—
|
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: tribal ancestor | Statement: [Achaeus, typeOfAncestralFigure, tribal ancestor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAncestralFigure Context triple: [Achaeus, typeOfAncestralFigure, tribal ancestor]
-
A.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
B.
ancestralStatus
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
C.
forefatherOf
Indicates that one person is an ancestor, typically from an earlier generation, of another person.
-
D.
isMythologicalFigureType
chosen
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
E.
ancestor
Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ece22908190a0941e23df7c774d |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:51 p.m.