Triple
T28196664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Show Must Go On |
E716466
|
entity |
| Predicate | leadVocalRecordingLocation |
P8088
|
FINISHED |
| Object | Montreux |
—
|
NE NERFINISHED |
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: Montreux | Statement: [The Show Must Go On, leadVocalRecordingLocation, Montreux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadVocalRecordingLocation Context triple: [The Show Must Go On, leadVocalRecordingLocation, Montreux]
-
A.
placeOfRecording
chosen
Indicates the location where an audio, video, or other recording was made.
-
B.
recordingLocationTour
Indicates the place where a tour-related recording (such as a live performance or tour event) was made.
-
C.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
D.
recordedInText
Indicates that an event, fact, or relationship is documented or mentioned within a particular text or written source.
-
E.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642d23ea481908f010394a925b83f |
completed | May 2, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:28 p.m.