Triple
T4956368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laius |
E111289
|
entity |
| Predicate | ordersAction |
P568
|
FINISHED |
| Object | exposure of his infant son Oedipus |
—
|
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: exposure of his infant son Oedipus | Statement: [Laius, ordersAction, exposure of his infant son Oedipus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordersAction Context triple: [Laius, ordersAction, exposure of his infant son Oedipus]
-
A.
order
chosen
Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
-
B.
ordersBy
Indicates that one entity arranges, sorts, or sequences another entity according to a specified criterion or set of criteria.
-
C.
orderClass
Indicates that one entity is classified into a particular order or category within a hierarchical or taxonomic system.
-
D.
orderGroup
Indicates that multiple individual orders are associated together as a single grouped order entity or batch.
-
E.
orderAuthority
Indicates that one entity has the formal power or right to issue orders or directives to another entity.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.