Triple
T16320260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS Worldport |
E396271
|
entity |
| Predicate | locatedAtAirportType |
P68256
|
FINISHED |
| Object | civil-military airport |
—
|
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: civil-military airport | Statement: [UPS Worldport, locatedAtAirportType, civil-military airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtAirportType Context triple: [UPS Worldport, locatedAtAirportType, civil-military airport]
-
A.
isLocatedAtAirportType
chosen
Indicates that one entity is situated at, or associated with, an airport of a specified type (e.g., international, regional, military).
-
B.
locatedAtAirportCode
Indicates that an entity is situated at, associated with, or occurs at the airport identified by a specific airport code.
-
C.
basedInAirport
Indicates that an entity has its primary location, operations, or headquarters situated at a specific airport.
-
D.
isLocatedAtAirportServingCity
Indicates that something is situated at an airport that provides service to a particular city.
-
E.
airportTypePresent
Indicates that a specific type or category of airport is present or exists in relation to the referenced entity.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b4ad448190b2b195a5e0032c6e |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.