Triple
T1930010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Reid International Airport |
E40921
|
entity |
| Predicate | renamedToCurrentName |
P21184
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Harry Reid International Airport, renamedToCurrentName, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedToCurrentName Context triple: [Harry Reid International Airport, renamedToCurrentName, 2021]
-
A.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
B.
renamedToReflect
Indicates that something has been given a new name specifically to better represent its nature, purpose, or current status.
-
C.
renamedToInclude
Indicates that an entity has been renamed so that its new name explicitly includes another specified element (such as a term, identifier, or component).
-
D.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb266dcb4819090be83556615d0db |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.