Triple
T25517715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary-General of Podemos |
E639554
|
entity |
| Predicate | isSpokespersonFor |
P114929
|
FINISHED |
| Object | Podemos |
—
|
NE NERFINISHED |
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: Podemos | Statement: [Secretary-General of Podemos, isSpokespersonFor, Podemos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokespersonFor Context triple: [Secretary-General of Podemos, isSpokespersonFor, Podemos]
-
A.
hasOfficialSpokespersons
Indicates that an entity is formally represented or spoken for by one or more designated spokespersons in an official capacity.
-
B.
speaksFor
chosen
Indicates that one entity expresses views, decisions, or positions on behalf of another entity.
-
C.
representedBySpeaker
Indicates that something is expressed, conveyed, or symbolized through a particular speaker as its representative voice or agent.
-
D.
representedFor
Indicates that one entity has acted or served as the official representative or proxy on behalf of another entity.
-
E.
spokesRepresent
Indicates that spokes act as representatives or intermediaries on behalf of another entity or central hub.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8339a8081908738ba23158091c9 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:57 p.m.