Triple
T5516874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KPUB |
E144705
|
entity |
| Predicate | servesMilitaryTraffic |
P34628
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [KPUB, servesMilitaryTraffic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesMilitaryTraffic Context triple: [KPUB, servesMilitaryTraffic, true]
-
A.
airportServesMilitaryTraffic
chosen
Indicates that the airport accommodates or handles military air traffic in addition to any other types of traffic.
-
B.
openedToMilitaryTraffic
Indicates that a route, facility, or passage has been made accessible and available for use by military vehicles or operations.
-
C.
servesGovernmentTraffic
Indicates that an entity provides services or functionality specifically for government-related network or data traffic.
-
D.
affectsAirTraffic
Indicates that one entity causes changes or disruptions to the normal flow, safety, or management of air traffic.
-
E.
replacedByForCivilTraffic
Indicates that one entity has been superseded or substituted by another specifically for purposes related to civil traffic matters.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5e8ce08190b7f5f2131bebcd4f |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.