Triple
T22484063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Know You Rider |
E555836
|
entity |
| Predicate | setlistRole |
P148390
|
FINISHED |
| Object | jam vehicle |
—
|
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: jam vehicle | Statement: [I Know You Rider, setlistRole, jam vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setlistRole Context triple: [I Know You Rider, setlistRole, jam vehicle]
-
A.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
-
B.
hasSetlistType
Indicates that an event or performance is associated with a particular type or category of setlist.
-
C.
musicSceneRole
Indicates the specific function or position an entity holds within a particular music scene or musical community.
-
D.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
E.
musicalEnsembleRole
Indicates the specific function or position an individual holds within a musical ensemble, such as performer, conductor, or composer.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3b03d881909e286a124c1a2b1c |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:49 p.m.