Triple
T18936918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsushima Air Base |
E463271
|
entity |
| Predicate | hasMilitaryControlTower |
P7890
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Matsushima Air Base, hasMilitaryControlTower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryControlTower Context triple: [Matsushima Air Base, hasMilitaryControlTower, yes]
-
A.
hasControlTower
chosen
Indicates that one entity possesses, hosts, or is equipped with a control tower that manages or oversees its operations.
-
B.
hasControlledAirspace
Indicates that a specified location or region falls within airspace where aircraft operations are regulated and managed by an aviation authority.
-
C.
airportServesMilitaryTraffic
Indicates that the airport accommodates or handles military air traffic in addition to any other types of traffic.
-
D.
towerManagedBy
Indicates that a particular tower is under the control, supervision, or administrative responsibility of a specified managing entity.
-
E.
militaryControl
Indicates that one entity exercises authoritative military power, command, or occupation over another entity or territory.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e7b87c81909dc29defb33c8e00 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.