Triple
T7277940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament Square, Edinburgh |
E163075
|
entity |
| Predicate | surfaceUse |
P1242
|
FINISHED |
| Object | pedestrian priority area |
—
|
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 priority area | Statement: [Parliament Square, Edinburgh, surfaceUse, pedestrian priority area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceUse Context triple: [Parliament Square, Edinburgh, surfaceUse, pedestrian priority area]
-
A.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
B.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
C.
surfaceType
chosen
Indicates the kind or classification of surface associated with an entity or interaction.
-
D.
surfaceCover
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
E.
surfaceBehavior
Indicates how an entity behaves or interacts specifically at or on its surface.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.