Triple
T31156984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nurse of Phaedra |
E794235
|
entity |
| Predicate | relationshipToPhaedra |
P207366
|
FINISHED |
| Object | servant |
—
|
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: servant | Statement: [Nurse of Phaedra, relationshipToPhaedra, servant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToPhaedra Context triple: [Nurse of Phaedra, relationshipToPhaedra, servant]
-
A.
relationshipToPriamAndHecuba
Indicates a familial or relational connection that an entity has specifically to both Priam and Hecuba.
-
B.
relationshipToHeracles
Indicates the specific familial or social relationship that an entity has to Heracles.
-
C.
relationshipToHecuba
Indicates a familial or social connection that an entity has with Hecuba.
-
D.
relationshipToDeianira
Indicates a specified type of relationship that one entity has to Deianira, such as familial, romantic, or social connection.
-
E.
hasRelationshipToCreon
Indicates that one entity has some form of relationship, connection, or association to the entity Creon.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:07 p.m.