Triple
T3102880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary’s Church, Sandwich |
E64759
|
entity |
| Predicate | locatedInTownCentre |
P25976
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [St Mary’s Church, Sandwich, locatedInTownCentre, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTownCentre Context triple: [St Mary’s Church, Sandwich, locatedInTownCentre, true]
-
A.
hasCityCentreLocation
chosen
Indicates that something is located in, or directly associated with, the central area of a city.
-
B.
locatedInResortTown
Indicates that something is situated within the boundaries of a town that is primarily known as a resort or vacation destination.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
E.
nearDowntown
Indicates that one location is situated close to or within a short distance of a city’s downtown area.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada26df128819086541db7680c8c24 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.