Triple
T20889632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astyanax |
E514373
|
entity |
| Predicate | roleInAndromache |
P141582
|
FINISHED |
| Object | dead son mourned by Andromache |
—
|
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: dead son mourned by Andromache | Statement: [Astyanax, roleInAndromache, dead son mourned by Andromache]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAndromache Context triple: [Astyanax, roleInAndromache, dead son mourned by Andromache]
-
A.
roleInHecuba
Indicates that an entity has a specific role or character assignment in the play *Hecuba*.
-
B.
roleInTrojanWar
Indicates the specific function, position, or part an entity played in the events of the Trojan War.
-
C.
takesSideInTrojanWar
Indicates that an entity participates in the Trojan War as a supporter of one of the opposing sides.
-
D.
relationshipToPriamAndHecuba
Indicates a familial or relational connection that an entity has specifically to both Priam and Hecuba.
-
E.
relationshipToHecuba
Indicates a familial or social connection that an entity has with Hecuba.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05d591481908c9c999db76760fc |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:46 p.m.