Triple
T29418091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matteo Salvini |
E746079
|
entity |
| Predicate | officeForStartTime |
P73495
|
FINISHED |
| Object | Deputy Prime Minister of Italy |
—
|
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: Deputy Prime Minister of Italy | Statement: [Matteo Salvini, officeForStartTime, Deputy Prime Minister of Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeForStartTime Context triple: [Matteo Salvini, officeForStartTime, Deputy Prime Minister of Italy]
-
A.
officeForStartEndTime
Indicates that an office is assigned or valid for a specific time interval defined by a start time and an end time.
-
B.
officeStartApproximate
Indicates that the start of a person’s term in office is known only approximately, not as an exact date.
-
C.
officeStartAfter
Indicates that one entity’s term or period in office begins after another specified time or event.
-
D.
officeStart
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
E.
officeStartFor
chosen
Indicates the time or date at which an entity begins its term, role, or period of service in an office or official position.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 28, 2026, 3:02 p.m.