Triple
T23809288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budget Policy Statement |
E589801
|
entity |
| Predicate | typeOfStrategy |
P31887
|
FINISHED |
| Object | broad, high-level fiscal strategy |
—
|
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: broad, high-level fiscal strategy | Statement: [Budget Policy Statement, typeOfStrategy, broad, high-level fiscal strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStrategy Context triple: [Budget Policy Statement, typeOfStrategy, broad, high-level fiscal strategy]
-
A.
strategyType
chosen
Indicates the specific kind or category of strategy associated with an entity or action.
-
B.
hasStratotype
Indicates that one entity serves as the designated standard or reference example (stratotype) for defining the stratigraphic characteristics of another entity.
-
C.
typeOfRule
Indicates that one rule is classified as a specific kind or category of another, more general rule.
-
D.
typeOfState
Indicates that one state is a specific kind or category of another, more general state.
-
E.
usesStrategy
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7549c44819099b9e7eb36747f38 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:56 p.m.