Triple
T5058856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Council of Aosta Valley |
E113973
|
entity |
| Predicate | headOfBodyTitle |
P10091
|
FINISHED |
| Object | President of the Regional Council of Aosta Valley |
—
|
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: President of the Regional Council of Aosta Valley | Statement: [Regional Council of Aosta Valley, headOfBodyTitle, President of the Regional Council of Aosta Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfBodyTitle Context triple: [Regional Council of Aosta Valley, headOfBodyTitle, President of the Regional Council of Aosta Valley]
-
A.
currentHeadTitle
chosen
Indicates the official title or position currently held by the head or leader of an entity.
-
B.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
C.
titleStart
Indicates that one entity’s title begins with the text or substring represented by the other entity.
-
D.
headOfHouseTitle
Indicates the formal title held by the person who serves as the head of a particular house or household.
-
E.
titleComponent
Indicates that one entity is a component or segment of the overall title associated with another 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74523434819092b8b15992073b5b |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.