Triple
T29550224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asiago |
E749745
|
entity |
| Predicate | warMemorial |
P115845
|
FINISHED |
| Object | Sacrario Militare del Leiten (Asiago War Memorial) |
—
|
NE NERFINISHED |
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: Sacrario Militare del Leiten (Asiago War Memorial) | Statement: [Asiago, warMemorial, Sacrario Militare del Leiten (Asiago War Memorial)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warMemorial Context triple: [Asiago, warMemorial, Sacrario Militare del Leiten (Asiago War Memorial)]
-
A.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember another entity.
-
B.
memorialSiteFor
chosen
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
-
C.
hasMemorialWall
Indicates that a place or entity includes or is associated with a wall dedicated to commemorating people, events, or memories.
-
D.
memorialLocatedAt
Indicates that a memorial is situated or found at a specific location.
-
E.
memorialType
Indicates the specific kind or category of memorial associated with an entity (e.g., plaque, statue, monument).
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf6b4ec8190a6ae2d496ea4408c |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:11 p.m.