Triple
T26408568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST |
E663895
|
entity |
| Predicate | AESCompetitionEndYear |
P161292
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [NIST, AESCompetitionEndYear, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AESCompetitionEndYear Context triple: [NIST, AESCompetitionEndYear, 2000]
-
A.
AESCompetitionStartYear
Indicates the calendar year in which an AES competition officially began.
-
B.
designCompetitionYear
Indicates the year in which a particular design competition took place or is associated with.
-
C.
recompetitionYear
Indicates the year in which a previously awarded or existing arrangement is opened again for competitive selection or bidding.
-
D.
competitionYears
Indicates the years during which the entities were involved in a particular competition or competitive event.
-
E.
designCompetitionWinYear
Indicates the year in which an entity won a particular design competition.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 26, 2026, 11:36 p.m.