Triple
T29362307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reno–Stead Airport |
E744623
|
entity |
| Predicate | FAA_LID_code |
P67437
|
FINISHED |
| Object | RTS |
—
|
NE NERFINISHED |
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: RTS | Statement: [Reno–Stead Airport, FAA_LID_code, RTS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FAA_LID_code Context triple: [Reno–Stead Airport, FAA_LID_code, RTS]
-
A.
airportCodeFAA
chosen
Indicates that an airport is identified by a specific FAA (Federal Aviation Administration) airport code.
-
B.
FAA_LID_of_same_airport
Indicates that two identifiers share the same FAA Location Identifier and therefore refer to the same airport.
-
C.
airfieldCode
Indicates that an entity is identified by a specific airfield code used to uniquely reference that airfield.
-
D.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
E.
FAAcode
Indicates that an entity (such as an airport or facility) is associated with a specific identifying code assigned by the Federal Aviation Administration (FAA).
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669894f608190941fed17608d9c2e |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:19 p.m.