Triple
T12461973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourbon Restoration in Spain |
E297818
|
entity |
| Predicate | inceptionEventDate |
P4201
|
FINISHED |
| Object | 29 December 1874 |
—
|
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: 29 December 1874 | Statement: [Bourbon Restoration in Spain, inceptionEventDate, 29 December 1874]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionEventDate Context triple: [Bourbon Restoration in Spain, inceptionEventDate, 29 December 1874]
-
A.
inceptionDate
chosen
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
B.
inceptionTime
Indicates the specific point in time when an entity, event, or relationship begins or is first established.
-
C.
inceptionWithin
Indicates that one event, process, or entity begins or is initiated entirely within the temporal or spatial bounds of another.
-
D.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
E.
inceptionOfPosition
Indicates the event or point in time at which a person or entity begins holding a particular position or role.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.