Triple
T24179675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at Montreux 1982 & 1985 |
E599382
|
entity |
| Predicate | containsPerformanceFromYear |
P69183
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Live at Montreux 1982 & 1985, containsPerformanceFromYear, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPerformanceFromYear Context triple: [Live at Montreux 1982 & 1985, containsPerformanceFromYear, 1982]
-
A.
yearOfPerformance
chosen
Indicates the specific calendar year in which a performance, event, or action took place.
-
B.
finalPerformanceYear
Indicates the year in which an entity’s performance or activity is recorded or recognized for the last time.
-
C.
raceYear
Indicates the specific calendar year in which a particular race event takes place.
-
D.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
E.
hasPartInYear
Indicates that something includes or contains a specific part, component, or segment that is associated with a particular year.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.