Triple
T37544045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harpe |
E933405
|
entity |
| Predicate | hasChildRole |
P27845
|
FINISHED |
| Object | Oenomaus, king of Pisa in Elis |
E274075
|
NE 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: Oenomaus, king of Pisa in Elis | Statement: [Harpe, hasChildRole, Oenomaus, king of Pisa in Elis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildRole Context triple: [Harpe, hasChildRole, Oenomaus, king of Pisa in Elis]
-
A.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
B.
hasChildIn
Indicates that one entity has a child who is located in, associated with, or present within another specified entity or context.
-
C.
has child
Indicates that one entity is the parent of another entity, which is its child.
-
D.
isChildIn
Indicates that one entity is the child (offspring or subordinate in a family or hierarchical structure) of another entity.
-
E.
hasRelativeRole
chosen
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
- F. None of above.
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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a7ec19c0819085d68adc48bf3ed9 |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:17 p.m.