Triple
T524250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl on Fire |
E10882
|
entity |
| Predicate | chronologyPosition |
P5172
|
FINISHED |
| Object | lead single of the album Girl on Fire |
—
|
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: lead single of the album Girl on Fire | Statement: [Girl on Fire, chronologyPosition, lead single of the album Girl on Fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyPosition Context triple: [Girl on Fire, chronologyPosition, lead single of the album Girl on Fire]
-
A.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
workChronologyPosition
chosen
Indicates the relative ordering or position of a work within a sequence of works, such as in a career, series, or catalog.
-
C.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
D.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
E.
positionInTimeScale
Indicates the specific point or interval an event or state occupies within a defined temporal scale or timeline.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b656c08190b387f21b06d99e68 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.