Triple
T1965240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1848 revolutions |
E42671
|
entity |
| Predicate | chronologicalFollowedBy |
P6880
|
FINISHED |
| Object | unification 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: unification of Italy | Statement: [1848 revolutions, chronologicalFollowedBy, unification of Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalFollowedBy Context triple: [1848 revolutions, chronologicalFollowedBy, unification of Italy]
-
A.
chronologicallyAfter
chosen
Indicates that one event or state occurs later in time than another.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
chronologicalFunction
Indicates a temporal relationship where one event or state functions to order, structure, or position another within a sequence of time.
-
D.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
E.
followsStoryOf
Indicates that one narrative, account, or storyline continues from, is based on, or is derived from the events or structure of another.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3aeb20081908b0d447d9fcdbaad |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.