Triple
T31110458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Prime Time Players |
E792928
|
entity |
| Predicate | firstRunEnd |
P201734
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [The Prime Time Players, firstRunEnd, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunEnd Context triple: [The Prime Time Players, firstRunEnd, 2014]
-
A.
firstRunEndDate
chosen
Indicates the date on which the initial or first run of something (such as a program, event, or process) concludes.
-
B.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
-
C.
secondRunEnd
Indicates the point or time at which a second run, iteration, or execution of an event or process concludes.
-
D.
firstRunStartDate
Indicates the date on which the first run or initial execution of something begins.
-
E.
firstRunTimePeriod
Indicates the initial time span or interval during which something first occurs, operates, or is in effect.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.