Triple
T18696158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajax's suicide scene |
E457119
|
entity |
| Predicate | timeWithinPlay |
P123426
|
FINISHED |
| Object | toward the end of the play Ajax |
—
|
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: toward the end of the play Ajax | Statement: [Ajax's suicide scene, timeWithinPlay, toward the end of the play Ajax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeWithinPlay Context triple: [Ajax's suicide scene, timeWithinPlay, toward the end of the play Ajax]
-
A.
playTime
Indicates the duration or specific time period during which an entity engages in playing or recreational activity with another entity or object.
-
B.
settingWithinPlay
chosen
Indicates that a particular setting (such as a location or environment) occurs within and is part of a specific play.
-
C.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
D.
timeToControl
Indicates the amount of time required for an entity to gain or establish control over another entity, process, or situation.
-
E.
timeOfYearPlayed
Indicates the specific time or season of the year during which an event or activity is performed or takes place.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e775408190996b4c613b83f185 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.