Triple
T34399278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misawa Airport |
E882928
|
entity |
| Predicate | isJointUseWithMilitary |
P71540
|
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: [Misawa Airport, isJointUseWithMilitary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJointUseWithMilitary Context triple: [Misawa Airport, isJointUseWithMilitary, true]
-
A.
isMilitaryShared
Indicates that military resources, responsibilities, or operations are jointly used, controlled, or participated in by multiple entities.
-
B.
isJointUseCivil
Indicates that a civil infrastructure asset or facility is intended for shared use by multiple parties, organizations, or functions.
-
C.
isJointCommand
Indicates that two or more entities share authority and responsibility together in directing or controlling a common operation or resource.
-
D.
isMilitaryOnly
Indicates that something is restricted exclusively to military use or participation, excluding civilians or non-military entities.
-
E.
isCivilMilitary
chosen
Indicates that an entity or relationship involves both civilian and military components or functions.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.