Triple
T31556680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary's Church, Ryde |
E805146
|
entity |
| Predicate | hasMainFacadeDirection |
P20200
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [St Mary's Church, Ryde, hasMainFacadeDirection, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainFacadeDirection Context triple: [St Mary's Church, Ryde, hasMainFacadeDirection, west]
-
A.
façadeOrientation
chosen
Indicates the directional orientation that a building’s façade faces relative to a reference (e.g., cardinal directions or a main street).
-
B.
hasFacadeSystem
Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
-
C.
isMajorFacadeOf
Indicates a relationship where one facade serves as the primary or most prominent exterior face of a building or structure.
-
D.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
E.
hasFacadeBy
Indicates that one entity’s façade (front-facing exterior surface) is designed, created, or provided by another entity.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00315632a8819092290f455babd7ee |
completed | May 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a002f54a0dc81909b0e54c5e110e67c |
completed | May 10, 2026, 7:10 a.m. |
Created at: April 30, 2026, 10:13 p.m.