Triple
T20012178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egeus |
E494614
|
entity |
| Predicate | threatensDaughterWith |
P60583
|
FINISHED |
| Object | death under Athenian law |
—
|
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: death under Athenian law | Statement: [Egeus, threatensDaughterWith, death under Athenian law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatensDaughterWith Context triple: [Egeus, threatensDaughterWith, death under Athenian law]
-
A.
threatenedToKill
chosen
Indicates that one entity has made a threat or expressed an intention to kill another entity.
-
B.
raisesAsDaughter
Indicates that one entity brings up and cares for another as their daughter, in a parental role.
-
C.
threatensToDestroy
Indicates that one entity has expressed an intention or warning that it will cause the complete ruin or elimination of another entity or object.
-
D.
possibleDaughter
Indicates that one entity may be the daughter of another, but this relationship is not certain or confirmed.
-
E.
heldByDaughterOf
Indicates that something is possessed, owned, or physically held by a person who is the daughter of another specified 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623773d88190826616a02d3c3e69 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.