Triple
T33395992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NQZ |
E855171
|
entity |
| Predicate | previousIATACodeOfAirport |
P198631
|
FINISHED |
| Object | TSE |
—
|
NE NERFINISHED |
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: TSE | Statement: [NQZ, previousIATACodeOfAirport, TSE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousIATACodeOfAirport Context triple: [NQZ, previousIATACodeOfAirport, TSE]
-
A.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
B.
previousICAOcode
Indicates that one entity was the former ICAO (International Civil Aviation Organization) code previously assigned to the other entity.
-
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.
airportCodeContext
Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
-
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. chosen
Provenance (4 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_69fef8c2cdd881908c6f44e4dfa5ffd0 |
completed | May 9, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:35 a.m.