Triple
T30263020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love in Limbo |
E769551
|
entity |
| Predicate | featuresPeriodElements |
P201278
|
FINISHED |
| Object | 1950s music |
—
|
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: 1950s music | Statement: [Love in Limbo, featuresPeriodElements, 1950s music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPeriodElements Context triple: [Love in Limbo, featuresPeriodElements, 1950s music]
-
A.
elementInPeriodicTable
Indicates that one entity is a chemical element that appears as an entry in the periodic table.
-
B.
chemicalElement
Indicates that one entity is a chemical element that constitutes, characterizes, or is otherwise fundamentally associated with the other entity.
-
C.
positionInPeriodicTable
Indicates the placement or location of a chemical element within the structure of the periodic table.
-
D.
featuresFictionalElement
Indicates that one entity includes, presents, or incorporates a fictional element (such as an imaginary character, place, object, or concept) as part of its content or composition.
-
E.
elementPeriod
Indicates the periodic table period (horizontal row) to which a given chemical element belongs.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69ffe6130698819099328fce92bb2784 |
completed | May 10, 2026, 1:57 a.m. |
Created at: April 29, 2026, 7:42 p.m.