Triple
T26140416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melekhovo |
E659499
|
entity |
| Predicate | hasFacilitySecurityLevel |
P98032
|
FINISHED |
| Object | strict regime |
—
|
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: strict regime | Statement: [Melekhovo, hasFacilitySecurityLevel, strict regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacilitySecurityLevel Context triple: [Melekhovo, hasFacilitySecurityLevel, strict regime]
-
A.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
-
B.
hasHighSecurityFacility
Indicates that an entity possesses or operates a facility characterized by a high level of security measures and protections.
-
C.
hasFacilityLevel
chosen
Indicates the degree or tier of capability, service, or infrastructure that a particular facility possesses.
-
D.
hasSecurityStandard
Indicates that an entity complies with, follows, or is governed by a specified security standard or framework.
-
E.
hasSecurityInfrastructure
Indicates that one entity possesses, implements, or is equipped with security-related systems, measures, or infrastructure in relation to another entity or context.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 8:19 p.m.