Triple
T19665905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at Massey Hall 1971 |
E472197
|
entity |
| Predicate | archivesPerformanceSeriesNumber |
P136877
|
FINISHED |
| Object | 03 |
—
|
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: 03 | Statement: [Live at Massey Hall 1971, archivesPerformanceSeriesNumber, 03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivesPerformanceSeriesNumber Context triple: [Live at Massey Hall 1971, archivesPerformanceSeriesNumber, 03]
-
A.
seriesBy
Indicates that one entity is the creator, author, or originator of a series to which the other entity belongs.
-
B.
seriesRun
Indicates that one entity is a specific run, edition, or installment within an ongoing series associated with another entity.
-
C.
seriesScore
Indicates the numerical outcome or standing of participants within a multi-part series, such as games, matches, or episodes, relative to one another.
-
D.
designationSeries
Indicates that one designation belongs to or is part of a broader series of related designations.
-
E.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
- F. None of above. chosen
Provenance (4 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416857c88190acb3adbf3e585fe5 |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.