Triple
T19083673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polydorus |
E467089
|
entity |
| Predicate | roleInHecuba |
P134308
|
FINISHED |
| Object | ghost narrator at beginning of play |
—
|
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: ghost narrator at beginning of play | Statement: [Polydorus, roleInHecuba, ghost narrator at beginning of play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHecuba Context triple: [Polydorus, roleInHecuba, ghost narrator at beginning of play]
-
A.
relationshipToHecuba
Indicates a familial or social connection that an entity has with Hecuba.
-
B.
roleInAlexiad
Indicates that one entity has a specific role or function within the context of the Alexiad (e.g., as an author, subject, or referenced figure).
-
C.
relationshipToDeianira
Indicates a specified type of relationship that one entity has to Deianira, such as familial, romantic, or social connection.
-
D.
takesSideInTrojanWar
Indicates that an entity participates in the Trojan War as a supporter of one of the opposing sides.
-
E.
roleAfterHeraclesDeath
Indicates the role or position an entity assumes or holds following the death of Heracles.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34600f88190bd96bcc2c5c08d14 |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.