Triple
T5431901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcestis |
E121513
|
entity |
| Predicate | tetralogyPosition |
P14675
|
FINISHED |
| Object | fourth play |
—
|
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: fourth play | Statement: [Alcestis, tetralogyPosition, fourth play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tetralogyPosition Context triple: [Alcestis, tetralogyPosition, fourth play]
-
A.
positionInTetrarchy
Indicates the specific role or rank an individual holds within a four-part governing or leadership structure (a tetrarchy).
-
B.
fourthPlace
chosen
Indicates that an entity holds the fourth position or rank in an ordered sequence, competition, or hierarchy.
-
C.
fourthTier
Indicates that one entity occupies the fourth level, rank, or tier in a hierarchical ordering or classification relative to others.
-
D.
fourthSingle
Indicates that an entity is the fourth individual item or occurrence in a sequence, considered on its own rather than as part of a group.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.