Triple
T7019513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G3 |
E162782
|
entity |
| Predicate | operatorSecondaryHubAirportIATA |
P75290
|
FINISHED |
| Object | GIG |
E209309
|
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: GIG | Statement: [G3, operatorSecondaryHubAirportIATA, GIG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GIG Context triple: [G3, operatorSecondaryHubAirportIATA, GIG]
-
A.
GIG
chosen
GIG is the IATA airport code for Rio de Janeiro–Galeão International Airport, the main international gateway serving Rio de Janeiro, Brazil.
-
B.
GIB
GIB is the IATA airport code for Gibraltar International Airport, which serves the British Overseas Territory of Gibraltar.
-
C.
GEM
GEM is the Growth Enterprise Market board of the Hong Kong Stock Exchange, designed for smaller, high-growth and emerging companies to raise capital.
-
D.
GIO
GIO is an Australian insurance company best known for providing a wide range of general insurance products, including car, home, and business insurance.
-
E.
GIP
GIP is the ISO 4217 currency code for the Gibraltar pound, the official currency of Gibraltar.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e77415e88190ab65137382f1b155 |
completed | March 27, 2026, 8:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c775707e30819088b311a1a87eee79 |
completed | March 28, 2026, 6:30 a.m. |
Created at: March 27, 2026, 2:34 p.m.