Triple
T28563158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Defense Authorization Act for Fiscal Year 2011 |
E722601
|
entity |
| Predicate | setPolicyFor |
P94281
|
FINISHED |
| Object | Department of Defense |
—
|
NE NERFINISHED |
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: Department of Defense | Statement: [National Defense Authorization Act for Fiscal Year 2011, setPolicyFor, Department of Defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setPolicyFor Context triple: [National Defense Authorization Act for Fiscal Year 2011, setPolicyFor, Department of Defense]
-
A.
policySetBy
chosen
Indicates that a particular policy is established, defined, or determined by a specific entity or authority.
-
B.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
C.
appliesPolicyOn
Indicates that one entity enforces, executes, or brings into effect a specific policy on another entity or context.
-
D.
setsSelectionPolicyFor
Indicates that one entity defines or configures the selection policy or criteria used by another entity.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6508cd720819085534e8463334767 |
completed | May 2, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:06 a.m.