Triple
T33049892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danaid trilogy |
E845693
|
entity |
| Predicate | placeInTetralogy |
P6115
|
FINISHED |
| Object | three tragedies of a four-play production |
—
|
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: three tragedies of a four-play production | Statement: [Danaid trilogy, placeInTetralogy, three tragedies of a four-play production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInTetralogy Context triple: [Danaid trilogy, placeInTetralogy, three tragedies of a four-play production]
-
A.
stonePlacement
Indicates the spatial arrangement or positioning of stones relative to a reference or surface.
-
B.
positionInTetrarchy
Indicates the specific role or rank an individual holds within a four-part governing or leadership structure (a tetrarchy).
-
C.
fourthPlace
Indicates that an entity holds the fourth position or rank in an ordered sequence, competition, or hierarchy.
-
D.
placeInSeries
chosen
Indicates the position or order that something occupies within a sequence or series.
-
E.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:24 a.m.