Triple
T5365784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Service Act 1989 |
E103125
|
entity |
| Predicate | establishesFunction |
P4780
|
FINISHED |
| Object | protection of national 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: protection of national security | Statement: [Security Service Act 1989, establishesFunction, protection of national security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesFunction Context triple: [Security Service Act 1989, establishesFunction, protection of national security]
-
A.
establishedBodyFunction
Indicates that an entity has created, defined, or instituted an official organizational structure, group, or body to perform a specific function or role.
-
B.
assignedFunction
chosen
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
C.
definesFunctioningOf
Indicates that one entity specifies or determines how another entity operates or functions.
-
D.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
E.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.