Triple
T28480015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIII Legislatura de España |
E720665
|
entity |
| Predicate | poderDelEstado |
P65960
|
FINISHED |
| Object | poder legislativo |
—
|
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: poder legislativo | Statement: [VIII Legislatura de España, poderDelEstado, poder legislativo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poderDelEstado Context triple: [VIII Legislatura de España, poderDelEstado, poder legislativo]
-
A.
hasStatePowers
chosen
Indicates that an entity possesses or exercises the official powers or authorities of a state-level government.
-
B.
occupationPower
Indicates a relationship where one party holds authoritative control, influence, or dominance over another within the context of an occupation or role.
-
C.
territorialPower
Indicates that an entity holds governing authority or control over a specific geographic territory.
-
D.
esParteDePoder
Indicates that something is a component or constituent element of a larger power or authority structure.
-
E.
powerClassification
Indicates how an entity’s power, strength, or influence is categorized or ranked within a defined system.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64ee8b3c08190a7efb9739393ca90 |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:54 a.m.