Triple
T29324398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicepresidente del Consiglio dei ministri |
E743602
|
entity |
| Predicate | livello |
P112328
|
FINISHED |
| Object | governo centrale |
—
|
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: governo centrale | Statement: [Vicepresidente del Consiglio dei ministri, livello, governo centrale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livello Context triple: [Vicepresidente del Consiglio dei ministri, livello, governo centrale]
-
A.
niveau
chosen
Indicates a relationship where an entity is associated with a particular level, degree, or stage within a scale, hierarchy, or progression.
-
B.
levels
Indicates that one entity adjusts, equalizes, or smooths out the height, intensity, or degree of another entity.
-
C.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
D.
definesLevel
Indicates that one entity specifies or establishes the degree, stage, or intensity at which another entity is set or operates.
-
E.
levelIDescription
Indicates that an entity provides a textual description of its difficulty or progression level.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66894ce4c8190b1104ea889b98a8e |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:25 p.m.