Triple
T8487797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubbard Field |
E200873
|
entity |
| Predicate | FAAIdentifier |
P420
|
FINISHED |
| Object | RNO |
E200871
|
NE 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: RNO | Statement: [Hubbard Field, FAAIdentifier, RNO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RNO Context triple: [Hubbard Field, FAAIdentifier, RNO]
-
A.
RNO
chosen
RNO is the three-letter IATA airport code for Reno–Tahoe International Airport, the primary commercial airport serving Reno, Nevada and the surrounding Lake Tahoe region.
-
B.
RNO
RNO is the stock ticker symbol for Renault, the French multinational automobile manufacturer listed on the Euronext Paris exchange.
-
C.
RNoN
RNoN is the abbreviation for the Royal Norwegian Navy, the maritime branch of Norway's armed forces.
-
D.
RZO
RZO is the ICAO airline designator used to identify Azores Airlines in international aviation operations.
-
E.
RNR
RNR is the abbreviation for the Royal Naval Reserve, the volunteer reserve force of the United Kingdom’s Royal Navy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe556b5188190b1124effd7445803 |
completed | March 31, 2026, 3:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4df197c48190812c5287119e5528 |
completed | April 2, 2026, 11:07 a.m. |
Created at: March 30, 2026, 6:13 p.m.