Triple
T12550315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SYRIZA |
E300078
|
entity |
| Predicate | keyPolicyFocus |
P25872
|
FINISHED |
| Object | anti-austerity measures |
—
|
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: anti-austerity measures | Statement: [SYRIZA, keyPolicyFocus, anti-austerity measures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyPolicyFocus Context triple: [SYRIZA, keyPolicyFocus, anti-austerity measures]
-
A.
keyPolicy
Indicates that a specified policy governs the creation, use, management, or access control of a particular key.
-
B.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
C.
keyTarget
chosen
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
-
D.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
E.
keyStateFocus
Indicates that a particular key or keyboard input currently has focus or is the active target for input events.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:58 p.m.