Triple
T2914803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Through the Fire |
E63774
|
entity |
| Predicate | isClassicIn |
P17136
|
FINISHED |
| Object | R&B ballads of the 1980s |
—
|
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: R&B ballads of the 1980s | Statement: [Through the Fire, isClassicIn, R&B ballads of the 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClassicIn Context triple: [Through the Fire, isClassicIn, R&B ballads of the 1980s]
-
A.
consideredClassic
chosen
Indicates that something is widely regarded or recognized as a classic within a particular field, genre, or context.
-
B.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
C.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
D.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
E.
isAnnualClassOf
Indicates that one entity is the regularly recurring yearly instance or cohort of a particular class or course.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0edb1ac81908b22ef60abb4a4df |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.