Triple
T9124738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian states |
E218942
|
entity |
| Predicate | unificationBegan |
P4318
|
FINISHED |
| Object | 1848 |
—
|
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: 1848 | Statement: [Italian states, unificationBegan, 1848]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unificationBegan Context triple: [Italian states, unificationBegan, 1848]
-
A.
unificationDate
chosen
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
B.
unificationLedTo
Indicates that a process of unifying previously separate entities resulted in or caused a particular outcome or state.
-
C.
historicalPeriodOfUnification
Indicates the historical time span during which separate entities were unified into a single political or organizational whole.
-
D.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
E.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b7436c8190b45bc6e4d6ec7066 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.