Triple
T8841670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolling in the Deep |
E210401
|
entity |
| Predicate | globalHit |
P84951
|
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: [Rolling in the Deep, globalHit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalHit Context triple: [Rolling in the Deep, globalHit, true]
-
A.
globalStatus
Indicates the overall state or condition of an entity as evaluated at a system-wide or global level.
-
B.
hits
Indicates a physical impact where one entity forcefully strikes or makes contact with another.
-
C.
globalRanking
Indicates the position or status of an entity relative to all comparable entities worldwide according to some ranking criteria.
-
D.
globalCondition
Indicates that a condition applies universally or system-wide rather than being limited to a specific local context or subset.
-
E.
globalResponse
Indicates a reaction, policy, or set of actions taken collectively at an international or worldwide level in response to a particular event or situation.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60876c6c8190b1b490e447e1cf4b |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:48 p.m.