Triple
T37649566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K12 |
E937133
|
entity |
| Predicate | isMilitarySensitiveArea |
P188563
|
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: [K12, isMilitarySensitiveArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitarySensitiveArea Context triple: [K12, isMilitarySensitiveArea, true]
-
A.
partOfMilitaryArea
Indicates that one entity is located within or belongs to a designated military-controlled area of another entity.
-
B.
isMilitaryInstallation
Indicates that a location functions as a military facility or base used for defense, training, operations, or related armed forces activities.
-
C.
hasDemilitarizedOrSpecialZones
Indicates that there exist designated areas between or within territories where military presence or activities are restricted or specially regulated.
-
D.
hasMilitaryPresence
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
E.
isProtectedAreaOf
Indicates that a designated protected area (such as a park or reserve) is established to conserve and manage a specific geographic region or natural feature.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbaa108ee48190b84d13df3ef3e365 |
completed | May 6, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.