Triple
T22256459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foals – What Went Down (production) |
E550105
|
entity |
| Predicate | emphasisOnElement |
P17414
|
FINISHED |
| Object | live band energy |
—
|
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: live band energy | Statement: [Foals – What Went Down (production), emphasisOnElement, live band energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasisOnElement Context triple: [Foals – What Went Down (production), emphasisOnElement, live band energy]
-
A.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
C.
designEmphasizes
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
D.
focusContrastWith
Indicates a relationship where one entity is highlighted or emphasized specifically in opposition or comparison to another, underscoring their differences.
-
E.
focusesLight
Indicates that one entity concentrates or directs light onto a specific area, object, or target.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c314308190a5eea84e1750158a |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.