Triple
T28777922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St John the Baptist Church, Glastonbury |
E726589
|
entity |
| Predicate | towerSignificance |
P57218
|
FINISHED |
| Object | landmark of Glastonbury |
—
|
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: landmark of Glastonbury | Statement: [St John the Baptist Church, Glastonbury, towerSignificance, landmark of Glastonbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerSignificance Context triple: [St John the Baptist Church, Glastonbury, towerSignificance, landmark of Glastonbury]
-
A.
towerLocation
Indicates that a tower is located at, or associated with, a specific place or geographic location.
-
B.
towerName
Indicates the specific name assigned to a tower in the relationship.
-
C.
towerCharacteristic
chosen
Indicates that a specified characteristic or feature is attributed to a tower.
-
D.
towerShape
Indicates that one entity has the physical form or outline of a tower in relation to another entity.
-
E.
towerDominates
Indicates that one tower stands out over another or its surroundings in a commanding or visually overpowering way.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:18 a.m.