Triple
T15511775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churchill War Rooms |
E368726
|
entity |
| Predicate | closedForMilitaryUse |
P23907
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Churchill War Rooms, closedForMilitaryUse, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForMilitaryUse Context triple: [Churchill War Rooms, closedForMilitaryUse, 1945]
-
A.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
-
B.
isMilitaryOnly
Indicates that something is restricted exclusively to military use or participation, excluding civilians or non-military entities.
-
C.
militaryUse
chosen
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
D.
closedForSafety
Indicates that an entity (such as a place, facility, or route) is temporarily unavailable or inaccessible due to safety concerns or hazards.
-
E.
closedToCivilianTraffic
Indicates that access along a route or at a location is restricted so that civilian vehicles or pedestrians are not allowed to use it.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04030c0208190a1931ea130075603 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:56 a.m.