Triple
T10010682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imma Be |
E198361
|
entity |
| Predicate | hasBeatSwitch |
P45596
|
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: [Imma Be, hasBeatSwitch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeatSwitch Context triple: [Imma Be, hasBeatSwitch, yes]
-
A.
hasBeat
Indicates that one entity has defeated or surpassed another in a competitive or comparative context.
-
B.
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.
-
C.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
-
D.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
-
E.
hasBPMApprox
Indicates an approximate beats-per-minute (BPM) value associated with an entity, rather than an exact measured tempo.
- 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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd3b68888190b8a325b52d57c5b8 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:52 p.m.