Triple
T26047349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WICA |
E647869
|
entity |
| Predicate | hasICAOCodePrefix |
P49384
|
FINISHED |
| Object | WI |
—
|
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: WI | Statement: [WICA, hasICAOCodePrefix, WI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasICAOCodePrefix Context triple: [WICA, hasICAOCodePrefix, WI]
-
A.
hasAirportCodePrefix
chosen
Indicates that an airport’s code begins with a specified sequence of characters.
-
B.
hasIcaoCodeFormat
Indicates that an entity’s ICAO code conforms to a specified structural or formatting pattern.
-
C.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
D.
previousICAOcode
Indicates that one entity was the former ICAO (International Civil Aviation Organization) code previously assigned to the other entity.
-
E.
hasIcaoAirport
Indicates that an entity is associated with an airport identified by a specific ICAO (International Civil Aviation Organization) airport 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065b4a248190a3fd8e9aee46d773 |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:10 a.m.