Triple
T16364901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storia d'Italia |
E397408
|
entity |
| Predicate | completionApproximateYear |
P22960
|
FINISHED |
| Object | 1530s |
—
|
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: 1530s | Statement: [Storia d'Italia, completionApproximateYear, 1530s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completionApproximateYear Context triple: [Storia d'Italia, completionApproximateYear, 1530s]
-
A.
workCompletionYear
Indicates the calendar year in which a particular work, project, or task was completed.
-
B.
approximateYearOfCompletion
chosen
Indicates the estimated calendar year in which something was completed, rather than an exact or confirmed year.
-
C.
originalCompletionYear
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
-
D.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
-
E.
approximateCompletionEra
Indicates the general historical period or time range during which something was completed, without specifying an exact date.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3bb5e481909669164a37d76b19 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.