Triple
T16650981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live Recordings 2004 |
E404600
|
entity |
| Predicate | performancesRecordedInYear |
P69183
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Live Recordings 2004, performancesRecordedInYear, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performancesRecordedInYear Context triple: [Live Recordings 2004, performancesRecordedInYear, 2004]
-
A.
annualPerformances
Indicates that performances or events occur on a yearly or once-per-year basis.
-
B.
notablePerformanceYear
Indicates the year in which an entity delivered a particularly significant or distinguished performance.
-
C.
yearOfPerformance
chosen
Indicates the specific calendar year in which a performance, event, or action took place.
-
D.
hasLivePerformancesRecorded
Indicates that live performances of an entity (such as a work, event, or artist) have been captured and stored as recordings.
-
E.
recordYear
Indicates the specific year in which something was recorded or documented.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf6cfc481909b183348c407e046 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.