Triple
T28388420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIS II |
E719084
|
entity |
| Predicate | purposeLimitation |
P125239
|
FINISHED |
| Object | maintenance of public security |
—
|
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: maintenance of public security | Statement: [SIS II, purposeLimitation, maintenance of public security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeLimitation Context triple: [SIS II, purposeLimitation, maintenance of public security]
-
A.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
B.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
C.
policyRestriction
chosen
Indicates that an entity is subject to a limiting rule, condition, or constraint imposed by a policy.
-
D.
governedForPurpose
Indicates that one entity exercises governance or control over another specifically to achieve a particular purpose or intended function.
-
E.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:11 a.m.