Triple
T24753662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mekoryuk Airport |
E619217
|
entity |
| Predicate | has code system |
P18653
|
FINISHED |
| Object | FAA LID |
—
|
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: FAA LID | Statement: [Mekoryuk Airport, has code system, FAA LID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has code system Context triple: [Mekoryuk Airport, has code system, FAA LID]
-
A.
hasCodeScheme
chosen
Indicates that something is associated with or organized according to a particular coding or classification scheme.
-
B.
hasStationCodeSystem
Indicates that an entity uses or is associated with a particular system for assigning or managing station codes.
-
C.
standardCodeSystem
Indicates that an entity uses or is associated with a recognized, authoritative coding or classification system as its reference standard.
-
D.
hasStandardCode
Indicates that an entity is associated with a recognized standard code that formally identifies or classifies it.
-
E.
regionCodeSystem
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:25 a.m.