Triple
T28480016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIII Legislatura de España |
E720665
|
entity |
| Predicate | denominaciónEnEspañol |
P2789
|
FINISHED |
| Object | VIII Legislatura de España |
—
|
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: VIII Legislatura de España | Statement: [VIII Legislatura de España, denominaciónEnEspañol, VIII Legislatura de España]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominaciónEnEspañol Context triple: [VIII Legislatura de España, denominaciónEnEspañol, VIII Legislatura de España]
-
A.
officialNameInSpanish
chosen
Indicates the officially recognized name of an entity when expressed in the Spanish language.
-
B.
hasNameInSpanish
Indicates that an entity is associated with a specific name expressed in the Spanish language.
-
C.
officialNameInCatalan
Indicates the officially recognized name of an entity when expressed in the Catalan language.
-
D.
historicalNameInSpanish
Indicates that an entity is known or referred to by a particular historical name when expressed in the Spanish language.
-
E.
hasOfficialShortNameInSpanish
Indicates that an entity possesses an officially recognized short form of its name expressed in the Spanish language.
- 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_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 2:54 a.m.