Triple
T31264613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfsschanze |
E797217
|
entity |
| Predicate | securityZones |
P18602
|
FINISHED |
| Object | three |
—
|
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: three | Statement: [Wolfsschanze, securityZones, three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityZones Context triple: [Wolfsschanze, securityZones, three]
-
A.
hasSecurityRegion
Indicates that an entity is associated with, governed by, or falls within a specific security region or security-related jurisdiction.
-
B.
demilitarizedZonePolicedBy
Indicates that a demilitarized zone is monitored, controlled, or kept secure by a specified policing authority or force.
-
C.
hasSecurityArea
chosen
Indicates that an entity is associated with, assigned to, or falls within a defined security-controlled area or zone.
-
D.
hasDRSZones
Indicates that one entity possesses, defines, or is associated with specific DRS (Disaster Recovery Site or similarly defined) zones.
-
E.
securityEnvironment
Indicates the overall conditions, threats, and protective measures that characterize the safety and risk context in which an entity operates.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 9:12 p.m.