Triple
T4341922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGAA |
E97801
|
entity |
| Predicate | belongsToCodeSystem |
P19933
|
FINISHED |
| Object | ICAO airport code system |
—
|
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: ICAO airport code system | Statement: [EGAA, belongsToCodeSystem, ICAO airport code system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCodeSystem Context triple: [EGAA, belongsToCodeSystem, ICAO airport code system]
-
A.
regionCodeSystem
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
-
B.
relatedCodeSet
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
C.
associatedLeagueCodeSystem
Indicates that there is a relationship linking an entity to the code system used by a particular league.
-
D.
hasAreaCodeSystem
Indicates that a telephone numbering plan, region, or communication system uses or is associated with a particular area code system.
-
E.
belongsToCatalogOf
chosen
Indicates that one item is included within, or is a member of, a particular catalog or collection.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351878c148190b384053479d41caf |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.