Triple
T9795013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Obsolete Man |
E237695
|
entity |
| Predicate | originalRunOrder |
P32788
|
FINISHED |
| Object | season 2 finale |
—
|
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: season 2 finale | Statement: [The Obsolete Man, originalRunOrder, season 2 finale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRunOrder Context triple: [The Obsolete Man, originalRunOrder, season 2 finale]
-
A.
originalOrder
chosen
Indicates that the entities are arranged or referenced according to their initial, unaltered sequence or configuration.
-
B.
originalRunType
Indicates the initial or primary category or mode under which a particular run, execution, or process was originally conducted.
-
C.
originalRunStatus
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
D.
originalRunDay
Indicates the specific day on which something (such as an event, program, or process) was first run or initially executed.
-
E.
originalRunIncluded
Indicates that an entity’s initial or primary execution, performance, or airing is contained within or forms part of another specified run or collection of runs.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda34916dc8190acef2ba003e56a33 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.