Triple
T19671641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larger Than Life |
E472346
|
entity |
| Predicate | chorusFeatures |
P54480
|
FINISHED |
| Object | anthemic hook |
—
|
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: anthemic hook | Statement: [Larger Than Life, chorusFeatures, anthemic hook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chorusFeatures Context triple: [Larger Than Life, chorusFeatures, anthemic hook]
-
A.
chorusFeature
chosen
Indicates that one entity participates in or is highlighted within the chorus section of another entity, such as a song or musical piece.
-
B.
chorus
Indicates that multiple entities jointly produce or participate in a coordinated vocal or expressive performance, typically as a unified group.
-
C.
chorusFocus
Indicates that the primary attention or emphasis is placed on a chorus or group performance rather than on individual elements.
-
D.
chorusType
Indicates the specific kind or category of chorus associated with an entity (e.g., type of vocal ensemble or choral grouping).
-
E.
chorusTheme
Indicates a relationship where a chorus centers on, expresses, or is organized around a particular theme.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416cb0bc8190ab27dd28eebb50e7 |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.