Triple
T26408543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST |
E663895
|
entity |
| Predicate | announcedAESSelectionYear |
P21538
|
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, announcedAESSelectionYear, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedAESSelectionYear Context triple: [NIST, announcedAESSelectionYear, 2000]
-
A.
campaignYear
Indicates the specific year in which a campaign takes place, is launched, or is associated with an entity.
-
B.
selectionYear
chosen
Indicates the year in which an entity was chosen or selected for a particular role, status, or inclusion.
-
C.
announcedExploratoryCommittee
Indicates that an individual has publicly declared the formation of an exploratory committee to consider running for a particular office or position.
-
D.
appliesToElectionYear
Indicates that something is relevant, valid, or in effect specifically for a given election year.
-
E.
candidacyYear
Indicates the specific year in which an entity is a candidate for a position, office, award, or similar selection process.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:36 p.m.