Triple
T20685644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DPS |
E508407
|
entity |
| Predicate | previousICAOCodeOfAirport |
P18649
|
FINISHED |
| Object | WRRR |
—
|
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: WRRR | Statement: [DPS, previousICAOCodeOfAirport, WRRR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousICAOCodeOfAirport Context triple: [DPS, previousICAOCodeOfAirport, WRRR]
-
A.
previousICAOcode
chosen
Indicates that one entity was the former ICAO (International Civil Aviation Organization) code previously assigned to the other entity.
-
B.
previousAirportName
Indicates the name that an airport was known by before its current name.
-
C.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
D.
formerIATAcode
Indicates that an entity previously held a specific IATA code, which is no longer its current assigned code.
-
E.
previousPrimaryAirportFor
Indicates that one airport was formerly the main or primary airport serving a particular location or entity before being replaced by another.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6beabf72881909771b6c6a81276d6 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:45 a.m.