Triple
T3655629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROK |
E77521
|
entity |
| Predicate | hasRelatedCodeSystem |
P14765
|
FINISHED |
| Object | ICAO airport code |
—
|
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 | Statement: [ROK, hasRelatedCodeSystem, ICAO airport code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedCodeSystem Context triple: [ROK, hasRelatedCodeSystem, ICAO airport code]
-
A.
relatedCodeSet
chosen
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
B.
hasCorrelativesSystem
Indicates that one entity possesses or employs a system of correlatives—structured, corresponding elements or forms that are systematically related to each other.
-
C.
regionCodeSystem
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
-
D.
relatedCode
Indicates that one code is associated with, linked to, or otherwise contextually connected to another code.
-
E.
associatedLeagueCodeSystem
Indicates that there is a relationship linking an entity to the code system used by a particular league.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3baf57c8190b72b5d1b910d9db6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.