Triple
T25039476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eusko Legebiltzarra |
E627068
|
entity |
| Predicate | headOfGovernmentChosen |
P12373
|
FINISHED |
| Object | Lehendakari |
—
|
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: Lehendakari | Statement: [Eusko Legebiltzarra, headOfGovernmentChosen, Lehendakari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfGovernmentChosen Context triple: [Eusko Legebiltzarra, headOfGovernmentChosen, Lehendakari]
-
A.
headOfGovernmentChosenBy
Indicates that the head of government is selected or appointed through the decision or authority of the specified chooser.
-
B.
headOfGovernment
Indicates that one entity serves as the chief executive authority or leader of the government of another entity.
-
C.
headOfGovernmentAtPassage
Indicates the person who was serving as head of government at the time a particular event, decision, or passage occurred.
-
D.
headOfGovernmentElection
chosen
Indicates the event or process in which a head of government is chosen or elected to office.
-
E.
headOfGovernmentSystem
Indicates the system or structure by which the head of government is selected, organized, and empowered within a political entity.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:08 a.m.