Triple
T38328069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Giles’ Square |
E1036844
|
entity |
| Predicate | hasPrimarySurfaceUse |
P125948
|
FINISHED |
| Object | pedestrian circulation |
—
|
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: pedestrian circulation | Statement: [St Giles’ Square, hasPrimarySurfaceUse, pedestrian circulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySurfaceUse Context triple: [St Giles’ Square, hasPrimarySurfaceUse, pedestrian circulation]
-
A.
hasSurfaceUse
Indicates that something is used or intended to be used on a surface (e.g., applied to, covering, or interacting with a surface).
-
B.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
C.
isPrimarilyUsedAs
chosen
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
D.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
-
E.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.