Triple
T9395605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coming Up (live at Glasgow) |
E226134
|
entity |
| Predicate | originalSongReleaseFormat |
P22610
|
FINISHED |
| Object | single |
—
|
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: single | Statement: [Coming Up (live at Glasgow), originalSongReleaseFormat, single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSongReleaseFormat Context triple: [Coming Up (live at Glasgow), originalSongReleaseFormat, single]
-
A.
firstReleaseFormat
chosen
Indicates the original medium or format in which something (such as a work or product) was first released.
-
B.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
-
C.
originalSong
Indicates that one entity is the source or initial version of a song from which another entity (such as a cover, remix, or adaptation) is derived.
-
D.
releasedAsSingleIn
Indicates that a musical work or track was issued as a standalone single in a specific year or time period.
-
E.
releasedAsSingleFor
Indicates that a particular track or song was issued as a standalone single specifically to promote or represent a given album, project, or release.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5112faa08190a8dd2c461d1e7a14 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.