Triple
T22483450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSO |
E555823
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | GSO |
—
|
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: GSO | Statement: [GSO, IATACode, GSO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GSO Context triple: [GSO, IATACode, GSO]
-
A.
GSO
GSO is a regional standards body that develops and harmonizes technical regulations and standards for the Gulf Cooperation Council member states.
-
B.
GSO
chosen
GSO is the three-letter FAA airport code for Piedmont Triad International Airport serving the Greensboro, North Carolina area.
-
C.
GSOFG
GSOFG was the abbreviated designation for the Group of Soviet Occupation Forces in Germany, the Soviet military formation responsible for administering and controlling occupied East Germany after World War II.
-
D.
GOS
GOS is the abbreviation for the Grand Orient of Spain, a major Masonic obedience historically active in Spanish Freemasonry.
-
E.
GOS
GOS is the acronym for the Global Observing System, an international network of instruments and facilities that continuously monitor the Earth's atmosphere, oceans, and land for weather and climate services.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3b03d881909e286a124c1a2b1c |
completed | April 29, 2026, 1:17 a.m. |
Created at: April 16, 2026, 8:49 p.m.