Triple
T19819559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 Emporis Skyscraper Award |
E476149
|
entity |
| Predicate | eligibleCompletionYear |
P95483
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [2006 Emporis Skyscraper Award, eligibleCompletionYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleCompletionYear Context triple: [2006 Emporis Skyscraper Award, eligibleCompletionYear, 2006]
-
A.
qualificationEndYear
Indicates the calendar year in which a qualification, certification, or course of study was completed or ended.
-
B.
upperLevelCompletionYear
Indicates the year in which an entity completed an upper-level stage of education, training, or qualification.
-
C.
typicallyCompletedInYearLevel
Indicates the usual school year level in which an activity, course, or requirement is completed.
-
D.
resumptionYear
Indicates the year in which an activity, process, or state that was previously halted starts again.
-
E.
yearTaken
chosen
Indicates the specific calendar year in which an action, event, or record associated with the subject was carried out or occurred.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fe0ff8819084bad251b76eff77 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.