Triple
T34852840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Monte Berico |
E1004644
|
entity |
| Predicate | locatedInShrineCity |
P205586
|
FINISHED |
| Object | Vicenza |
E63542
|
NE 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: Vicenza | Statement: [Our Lady of Monte Berico, locatedInShrineCity, Vicenza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInShrineCity Context triple: [Our Lady of Monte Berico, locatedInShrineCity, Vicenza]
-
A.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
B.
containsShrine
Indicates that one entity includes or has within its boundaries a shrine associated with it.
-
C.
possibleShrineLocation
Indicates that a location is suitable or designated as a potential site where a shrine could be placed or constructed.
-
D.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
-
E.
recognizedAsShrineBy
Indicates that something is regarded or designated as a shrine by a particular person, group, or authority.
- F. None of above. chosen
Provenance (5 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b2599c3c8190b7b9749e02184e7b |
completed | June 21, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4 p.m.