Triple
T36058045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satellite Terminal A |
E1043000
|
entity |
| Predicate | locatedAtAirportWithICAOCode |
P98491
|
FINISHED |
| Object | WMKK |
E318231
|
NE 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: WMKK | Statement: [Satellite Terminal A, locatedAtAirportWithICAOCode, WMKK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtAirportWithICAOCode Context triple: [Satellite Terminal A, locatedAtAirportWithICAOCode, WMKK]
-
A.
locatedAtAirportCode
chosen
Indicates that an entity is situated at, associated with, or occurs at the airport identified by a specific airport code.
-
B.
isLocatedAtAirportType
Indicates that one entity is situated at, or associated with, an airport of a specified type (e.g., international, regional, military).
-
C.
locatedInAirportArea
Indicates that something is situated within the grounds or designated area of an airport.
-
D.
basedInAirport
Indicates that an entity has its primary location, operations, or headquarters situated at a specific airport.
-
E.
airportLocatedIn
Indicates that an airport is geographically situated within a specific administrative or territorial area.
- F. None of above.
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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cba591908190978c635582500aa8 |
completed | June 22, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.