Triple
T5479179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Policy Database |
E123428
|
entity |
| Predicate | policyEntryIncludes |
P18283
|
FINISHED |
| Object | source IP address selectors |
—
|
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: source IP address selectors | Statement: [Security Policy Database, policyEntryIncludes, source IP address selectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyEntryIncludes Context triple: [Security Policy Database, policyEntryIncludes, source IP address selectors]
-
A.
containsPolicyOn
Indicates that one entity includes, references, or incorporates a specific policy within it.
-
B.
evaluationCriteriaInclude
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
C.
policyElement
Indicates that something is a component or constituent part of a broader policy.
-
D.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
-
E.
hasEntryOn
chosen
Indicates that one entity contains or includes an entry, record, or listing about another entity.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.