Triple
T29808624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knights of Cydonia |
E756899
|
entity |
| Predicate | typicalLiveSetCloser |
P55758
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Knights of Cydonia, typicalLiveSetCloser, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLiveSetCloser Context triple: [Knights of Cydonia, typicalLiveSetCloser, yes]
-
A.
finalConcert
Indicates that an event is the concluding or last concert in a series, tour, or sequence of performances.
-
B.
hasLiveOutroImprovisations
Indicates that an entity includes or features improvised material performed live during its outro section.
-
C.
closingEnsembleType
Indicates the type or category of ensemble that performs or appears at the closing portion of an event or work.
-
D.
finalSong
chosen
Indicates that a song is the last or concluding piece within a sequence, collection, or performance.
-
E.
closingChoraleFirstVersion
Indicates that the relationship involves the first version of a closing chorale section, typically marking an initial or original form of the concluding choral passage.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a03008316dc8190a9f6faf48d25a4f8 |
completed | May 12, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a030023e66881909ea79f1365ab538a |
completed | May 12, 2026, 10:25 a.m. |
Created at: April 29, 2026, 5:22 p.m.