Triple
T34162805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aethalides |
E876322
|
entity |
| Predicate | hasMortalLineage |
P86225
|
FINISHED |
| Object | Eupolemeia |
—
|
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: Eupolemeia | Statement: [Aethalides, hasMortalLineage, Eupolemeia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMortalLineage Context triple: [Aethalides, hasMortalLineage, Eupolemeia]
-
A.
hasMortalOrSemiDivineAncestry
Indicates that an entity descends from, or is otherwise ancestrally connected to, beings who are mortal or possess semi-divine (partly divine) status.
-
B.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
-
C.
mortalParent
chosen
Indicates that one entity is the biological or adoptive parent of another and is subject to mortality (i.e., not immortal).
-
D.
hasHomininTaxon
Indicates that an entity is associated with, classified under, or belongs to a particular hominin taxonomic group.
-
E.
hasNotableLineage
Indicates that an entity descends from, or is associated with, a distinguished or historically significant family, ancestry, or heritage.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
Created at: May 1, 2026, 1:54 a.m.