Triple
T28628008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia servers |
E724571
|
entity |
| Predicate | securityPracticeIncludes |
P174702
|
FINISHED |
| Object | regular security updates |
—
|
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: regular security updates | Statement: [Wikimedia servers, securityPracticeIncludes, regular security updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityPracticeIncludes Context triple: [Wikimedia servers, securityPracticeIncludes, regular security updates]
-
A.
securityPillar
Indicates that one entity functions as a foundational security pillar or core security domain in relation to another entity.
-
B.
securityPrinciple
Indicates that an entity embodies, defines, or is governed by a fundamental rule, guideline, or concept related to security.
-
C.
securityProgram
Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
-
D.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
E.
hasSecurityArchitecture
Indicates that an entity is associated with or defined by a particular security architecture design or framework.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 28, 2026, 4:36 a.m.