Triple
T33639295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Dead |
E861786
|
entity |
| Predicate | featuresBeatSwitches |
P45596
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [King’s Dead, featuresBeatSwitches, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBeatSwitches Context triple: [King’s Dead, featuresBeatSwitches, true]
-
A.
featuresBeatSwitch
chosen
Indicates that one entity includes or incorporates a change in rhythmic pattern or beat, typically marking a transition within a sequence or composition.
-
B.
featuresRhythm
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
-
C.
usesBeatFrom
Indicates that one entity employs or incorporates the rhythmic pattern, instrumental backing, or beat originally created for or associated with another entity.
-
D.
featuresDrumMachine
Indicates that something includes or makes use of a drum machine as part of its composition or functionality.
-
E.
usesBeatType
Indicates that an entity employs or is based on a particular type or pattern of beat (rhythmic structure).
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01e993fec0819090cc397218515e88 |
completed | May 11, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_6a01e57594188190a2354f48cf71b48c |
completed | May 11, 2026, 2:19 p.m. |
Created at: May 1, 2026, 1:42 a.m.