Triple
T18034587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Podemos |
E431473
|
entity |
| Predicate | antiAusterity |
P33291
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Podemos, antiAusterity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antiAusterity Context triple: [Podemos, antiAusterity, true]
-
A.
advocatesAgainst
chosen
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
B.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
C.
opposition
Indicates a relationship in which one entity actively resists, disagrees with, or is positioned against another entity, idea, or action.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
opposedAdministration
Indicates that one entity actively resisted, challenged, or worked against the governance, policies, or authority exercised by another entity or administration.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be38766c8190ae95701f4575469c |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.