Triple
T29830249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sledgehammer (live performances) |
E757492
|
entity |
| Predicate | typicalSetlistPosition |
P199924
|
FINISHED |
| Object | encore |
—
|
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: encore | Statement: [Sledgehammer (live performances), typicalSetlistPosition, encore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSetlistPosition Context triple: [Sledgehammer (live performances), typicalSetlistPosition, encore]
-
A.
typicalSetlistStatus
chosen
Indicates the usual or expected status of an item within a standard or commonly performed setlist.
-
B.
featuredInTourSetlistOf
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
C.
performerPosition
Indicates the spatial or role-based placement of a performer relative to a performance context or other participants.
-
D.
hasSetlistSpanning
Indicates that a setlist covers or includes items from a specified range, period, or collection.
-
E.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0302d9d2d88190b20429530775b035 |
completed | May 12, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_6a0302289128819085428f3d544c2fb9 |
completed | May 12, 2026, 10:34 a.m. |
Created at: April 29, 2026, 5:33 p.m.