Triple
T19263684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rota International Airport |
E481713
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | GRO |
—
|
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: GRO | Statement: [Rota International Airport, FAA LID, GRO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GRO Context triple: [Rota International Airport, FAA LID, GRO]
-
A.
GRO
chosen
GRO is the FAA airport code assigned to Rota International Airport, a public airport serving the island of Rota in the Northern Mariana Islands.
-
B.
GRO
GRO is the commonly used acronym for the Compton Gamma Ray Observatory, a NASA space telescope that studied high-energy gamma-ray sources in the universe.
-
C.
GRO
GRO is the station code used to identify Grove Street station on the Newark Light Rail system in New Jersey.
-
D.
GRO
GRO is the IATA airport code for Girona–Costa Brava Airport, a regional airport in Catalonia, Spain that serves the city of Girona and the nearby Costa Brava tourist area.
-
E.
GROM
GROM is Poland’s elite special operations unit renowned for high-risk counterterrorism, hostage rescue, and unconventional warfare missions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8bce6881908395836960762672 |
completed | April 20, 2026, 10:10 a.m. |
Created at: April 10, 2026, 1:28 p.m.