Triple
T19818708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Italian campaign |
E476127
|
entity |
| Predicate | hasDateOfClimacticBattle |
P12233
|
FINISHED |
| Object | 14 June 1800 |
—
|
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: 14 June 1800 | Statement: [Second Italian campaign, hasDateOfClimacticBattle, 14 June 1800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDateOfClimacticBattle Context triple: [Second Italian campaign, hasDateOfClimacticBattle, 14 June 1800]
-
A.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
B.
battleOccurredOn
chosen
Indicates that a specific battle took place at or on a particular location or date.
-
C.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
refersToPersonNotableBattle
Indicates that a person is associated with or identified by a specific notable battle in which they played a significant 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fc8b94819095fd5240f33b6713 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.