Triple
T25420743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fatherhood of Orpheus |
E636976
|
entity |
| Predicate | hasTraditionalFather |
P168030
|
FINISHED |
| Object | Oeagrus |
—
|
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: Oeagrus | Statement: [fatherhood of Orpheus, hasTraditionalFather, Oeagrus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalFather Context triple: [fatherhood of Orpheus, hasTraditionalFather, Oeagrus]
-
A.
hasHolderFather
Indicates that an entity has a father who serves as the holder or custodian of that entity.
-
B.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
C.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
D.
paternalStatus
Indicates the nature or condition of a paternal relationship that an entity has to another (e.g., being a father, presumed father, or having a specific paternal role or status).
-
E.
oftenHasFather
Indicates that the subject entity frequently or typically has a father relationship to the specified object entity.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 21, 2026, 1:56 p.m.