Triple
T17363142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Management of the Treasury Department |
E422118
|
entity |
| Predicate | usesPolicyType |
P105152
|
FINISHED |
| Object | organizational policy |
—
|
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: organizational policy | Statement: [Office of Management of the Treasury Department, usesPolicyType, organizational policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPolicyType Context triple: [Office of Management of the Treasury Department, usesPolicyType, organizational policy]
-
A.
usedPolicy
Indicates that an entity applied or followed a particular policy in carrying out an action or decision.
-
B.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
-
C.
usesPolicyRate
Indicates that one entity applies or bases its actions or decisions on a specified policy interest rate.
-
D.
appliesPolicyType
chosen
Indicates that a specific policy type is applied to or enforced on a given entity or context.
-
E.
usagePolicy
Indicates the rules or conditions governing how something may be used or accessed.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4e3c3481909dfaa00334c5010e |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.