Triple
T20889631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astyanax |
E514373
|
entity |
| Predicate | roleInTheTrojanWomen |
P134559
|
FINISHED |
| Object | child sacrificed after the fall of Troy |
—
|
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: child sacrificed after the fall of Troy | Statement: [Astyanax, roleInTheTrojanWomen, child sacrificed after the fall of Troy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheTrojanWomen Context triple: [Astyanax, roleInTheTrojanWomen, child sacrificed after the fall of Troy]
-
A.
roleInHecuba
Indicates that an entity has a specific role or character assignment in the play *Hecuba*.
-
B.
roleInTrojanWar
chosen
Indicates the specific function, position, or part an entity played in the events of the Trojan War.
-
C.
relationshipToHecuba
Indicates a familial or social connection that an entity has with Hecuba.
-
D.
roleInAnalects
Indicates that one entity has a specific role, function, or status within the context of the Analects.
-
E.
dramaticStructureRole
Indicates the specific function or role an element plays within the overall dramatic structure of a narrative or performance.
- 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_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. |
Created at: April 16, 2026, 12:46 p.m.