Triple
T1235672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grammy Award for Best Musical Theater Album |
E26541
|
entity |
| Predicate | currentNameEffectiveFrom |
P21184
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Grammy Award for Best Musical Theater Album, currentNameEffectiveFrom, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentNameEffectiveFrom Context triple: [Grammy Award for Best Musical Theater Album, currentNameEffectiveFrom, 2012]
-
A.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
-
B.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
-
C.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
-
D.
currentISOCodeEffectiveFrom
Indicates the date and time from which the current ISO code for an entity becomes valid or officially in effect.
-
E.
currentNameUsedFrom
chosen
Indicates that an entity’s currently used name has been in effect starting from a specified point in time or source.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf169868819090cfab7e34c40c67 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.