Triple
T23934518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakhchivan International Airport |
E602593
|
entity |
| Predicate | isMilitaryShared |
P154413
|
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: [Nakhchivan International Airport, isMilitaryShared, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitaryShared Context triple: [Nakhchivan International Airport, isMilitaryShared, yes]
-
A.
isMilitaryOnly
Indicates that something is restricted exclusively to military use or participation, excluding civilians or non-military entities.
-
B.
isMilitaryCommand
Indicates that one entity holds formal military authority or command over another entity or group.
-
C.
isMilitarized
Indicates that an entity is organized, equipped, or structured according to military principles, forces, or purposes.
-
D.
isUnifiedMilitaryOf
Indicates that an entity serves as the single, consolidated military force representing or defending another entity (such as a state, alliance, or organization).
-
E.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
- F. None of above. chosen
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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9da9c4819085880c6ad521d7ed |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9 p.m.