Triple
T28757070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysippus |
E731699
|
entity |
| Predicate | relationshipWithLaius |
P202283
|
FINISHED |
| Object | beloved of Laius |
—
|
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: beloved of Laius | Statement: [Chrysippus, relationshipWithLaius, beloved of Laius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithLaius Context triple: [Chrysippus, relationshipWithLaius, beloved of Laius]
-
A.
hasRelationshipToCreon
Indicates that one entity has some form of relationship, connection, or association to the entity Creon.
-
B.
relationshipToDeianira
Indicates a specified type of relationship that one entity has to Deianira, such as familial, romantic, or social connection.
-
C.
relationshipToPriamAndHecuba
Indicates a familial or relational connection that an entity has specifically to both Priam and Hecuba.
-
D.
relationToOdysseus
Indicates the specific familial, social, or narrative relationship that one entity has to Odysseus.
-
E.
conceptionOfAegisthus
Indicates the event or relationship in which Aegisthus is conceived, linking his parents to his origin.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_6a006ef80ce88190b5e3a2b261409d44 |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 28, 2026, 6:10 a.m.