Triple
T6826334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCLP |
E157023
|
entity |
| Predicate | hasICAORegion |
P25279
|
FINISHED |
| Object | GC |
—
|
LITERAL 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: GC | Statement: [GCLP, hasICAORegion, GC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasICAORegion Context triple: [GCLP, hasICAORegion, GC]
-
A.
associatedAirportICAOSubregion
Indicates a relationship where an airport is linked to the specific ICAO-defined subregion in which it is located or with which it is operationally associated.
-
B.
hasAirportCodeRegion
chosen
Indicates that an airport code is associated with, or belongs to, a specific geographic or administrative region.
-
C.
ICAOTypeDesignator
Indicates the standardized aircraft type code assigned by ICAO that specifies the model or family of an aircraft used in aviation operations and documentation.
-
D.
associatedWithICAOcode
Indicates a relationship where an entity is linked to, or identified by, a specific ICAO (International Civil Aviation Organization) code.
-
E.
ICAOEngineCode
Indicates that an engine is identified or classified by a specific ICAO (International Civil Aviation Organization) engine code.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d58375248190935dd38d618994e3 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.