Triple
T30727468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priory Gardens |
E782317
|
entity |
| Predicate | hasBuildingAtEdge |
P14728
|
FINISHED |
| Object | The Priory, Orpington |
—
|
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: The Priory, Orpington | Statement: [Priory Gardens, hasBuildingAtEdge, The Priory, Orpington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingAtEdge Context triple: [Priory Gardens, hasBuildingAtEdge, The Priory, Orpington]
-
A.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
B.
containsBuilding
chosen
Indicates that one location or area includes a building within its boundaries.
-
C.
hasBuildingLocation
Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
-
D.
hasBuildingFunction
Indicates that a building is used for or serves a particular function or purpose.
-
E.
hasNearbyCivicBuilding
Indicates that one entity is located close to, or in the immediate vicinity of, a civic building such as a government, public service, or community facility.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 8:37 p.m.