Triple
T30690418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One St Peter’s Square, Manchester |
E781308
|
entity |
| Predicate | hasPublicSpaceAtGroundLevel |
P37084
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [One St Peter’s Square, Manchester, hasPublicSpaceAtGroundLevel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSpaceAtGroundLevel Context triple: [One St Peter’s Square, Manchester, hasPublicSpaceAtGroundLevel, yes]
-
A.
hasGroundFloor
Indicates that a building or structure includes a ground-level floor as part of its layout or design.
-
B.
hasPublicSpaces
chosen
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
C.
hasFloorsAboveGround
Indicates that an entity (typically a building or structure) possesses a specified number of floors that are located above ground level.
-
D.
hasGroundFloorUse
Indicates that a building or structure is associated with a specific functional use assigned to its ground floor level.
-
E.
roofAccessibleToPublic
Indicates that the roof of a structure is legally or physically open and available for use or access by the general public.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 8:33 p.m.