Triple
T924855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oedipus |
E19960
|
entity |
| Predicate | unknowinglyMarried |
P22415
|
FINISHED |
| Object | his mother |
—
|
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: his mother | Statement: [Oedipus, unknowinglyMarried, his mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unknowinglyMarried Context triple: [Oedipus, unknowinglyMarried, his mother]
-
A.
marriedInto
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
B.
neverMarried
Indicates that the subject has not been legally married to any partner at any time up to the present.
-
C.
connectedThroughMarriageVia
Indicates that two entities are related to each other by a marital connection that is mediated through one or more intermediate spouses or in-laws, rather than by a direct marriage between them.
-
D.
hasMarriagePlot
Indicates that the work’s narrative centrally involves courtship, romantic relationships, or the progression toward marriage as a key plot element.
-
E.
marriageCharacterization
Indicates how a marriage is described, evaluated, or characterized in terms of its qualities, dynamics, or nature.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2970a4c8190b22cb2fd4706f62b |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b385176081909e3e8c3f647c1fd4 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.