Triple
T17795990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlusconi II Cabinet |
E444292
|
entity |
| Predicate | timeInOfficeApprox |
P36144
|
FINISHED |
| Object | almost four years |
—
|
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: almost four years | Statement: [Berlusconi II Cabinet, timeInOfficeApprox, almost four years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInOfficeApprox Context triple: [Berlusconi II Cabinet, timeInOfficeApprox, almost four years]
-
A.
timeInOfficeCharacteristic
Indicates a characteristic or attribute specifically related to the duration or period an entity spends in office or in a particular official role.
-
B.
termInOffice
Indicates the period during which an individual officially holds a particular office or position.
-
C.
timeInNationalGovernment
Indicates the duration that an entity has served within a national-level government.
-
D.
timeInOfficeBeginsIn
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
E.
timeInOfficeRelation
chosen
Indicates a temporal relationship specifying the duration or period that an entity holds or held a particular office or 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fafc2c8190b28e791267c47e3c |
completed | April 19, 2026, 7:44 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.