Triple
T6825399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSPP |
E157001
|
entity |
| Predicate | typeOfPolicyBody |
P73269
|
FINISHED |
| Object | strategy and policy office |
—
|
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: strategy and policy office | Statement: [OSPP, typeOfPolicyBody, strategy and policy office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPolicyBody Context triple: [OSPP, typeOfPolicyBody, strategy and policy office]
-
A.
hasPolicyBody
Indicates that an entity is associated with, or defined by, a specific policy document or policy text.
-
B.
typeOfBody
Indicates that one entity is the classification or kind of physical body that the other entity is.
-
C.
publicBodyType
Indicates the classification or category of a public body (such as its organizational or legal type) within a governmental or public-sector context.
-
D.
includesTypeOfBody
Indicates that one entity encompasses or contains another entity classified as a specific type of body (e.g., physical, celestial, or organizational body).
-
E.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d581ea5881908ba78c6bf1ce58ee |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:18 p.m.