Triple
T24398921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold as Ice |
E615111
|
entity |
| Predicate | isByBandType |
P72274
|
FINISHED |
| Object | British-American rock band |
—
|
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: British-American rock band | Statement: [Cold as Ice, isByBandType, British-American rock band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isByBandType Context triple: [Cold as Ice, isByBandType, British-American rock band]
-
A.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other entity.
-
B.
bandType
chosen
Indicates the specific kind or category of band that an entity belongs to or is associated with.
-
C.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
D.
hasBandNumber
Indicates that an entity is associated with a specific band identification number.
-
E.
usesBand
Indicates that one entity employs or makes use of a particular band (such as a group, frequency band, or band resource) in performing an action or fulfilling a function.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294d91d1081909a2255569f2600e2 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.