Triple
T6954336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How to Rock |
E161203
|
entity |
| Predicate | originalRunYearStart |
P10224
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [How to Rock, originalRunYearStart, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRunYearStart Context triple: [How to Rock, originalRunYearStart, 2012]
-
A.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
B.
productionStartYear
Indicates the year in which the production of an item, work, or entity first began.
-
C.
originYear
Indicates the year in which something first originated, was created, or began.
-
D.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
-
E.
firstSeriesYear
chosen
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dace1a94819095311e4288f01784 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.