Triple
T33784791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | financial stability authority |
E865756
|
entity |
| Predicate | mayUseTool |
P9928
|
FINISHED |
| Object | macroprudential policy instruments |
—
|
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: macroprudential policy instruments | Statement: [financial stability authority, mayUseTool, macroprudential policy instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayUseTool Context triple: [financial stability authority, mayUseTool, macroprudential policy instruments]
-
A.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
B.
canUse
chosen
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
usesToolFor
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
D.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
E.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.