Triple
T32235255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campana dei Caduti |
E823448
|
entity |
| Predicate | originallyInaugurated |
P203428
|
FINISHED |
| Object | 1925 |
—
|
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: 1925 | Statement: [Campana dei Caduti, originallyInaugurated, 1925]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyInaugurated Context triple: [Campana dei Caduti, originallyInaugurated, 1925]
-
A.
inauguratedWith
Indicates that an event, position, or institution was formally initiated or opened through a specific ceremony, action, or accompanying element.
-
B.
inaugurated
Indicates that a person is formally introduced or installed into an official position, office, or role through a ceremonial event.
-
C.
inauguratedAsPartOf
Indicates that an inauguration event occurred as a component or phase of a larger event, process, or initiative.
-
D.
helpedInaugurate
Indicates that one entity played a role in initiating, launching, or formally beginning another entity, event, or process.
-
E.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
- F. None of above. chosen
Provenance (4 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a017bc21b048190b9c680013de203b6 |
completed | May 11, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_6a017aa09c4481909c3b55e0cd13501e |
completed | May 11, 2026, 6:43 a.m. |
| PDg | Predicate description generation | batch_6a017bc16860819090d47f1c2db1ca88 |
completed | May 11, 2026, 6:48 a.m. |
Created at: May 1, 2026, 12:39 a.m.