Triple
T30286808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grafton Street |
E770259
|
entity |
| Predicate | pedestrianZoneStatus |
P46481
|
FINISHED |
| Object | mainly pedestrianised |
—
|
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: mainly pedestrianised | Statement: [Grafton Street, pedestrianZoneStatus, mainly pedestrianised]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianZoneStatus Context triple: [Grafton Street, pedestrianZoneStatus, mainly pedestrianised]
-
A.
hasPedestrianZoneStatus
chosen
Indicates whether an area or segment is designated as a pedestrian-only or pedestrian-priority zone and its corresponding status.
-
B.
pedestrianRestrictions
Indicates that there are specific rules or limitations governing where or how pedestrians may travel or access an area.
-
C.
pedestrianizedAreas
Indicates areas where vehicle traffic is restricted or removed so that pedestrians have priority use of the space.
-
D.
pedestrianActivity
Indicates that an entity is engaged in or associated with walking or other on-foot movement or behavior.
-
E.
isPedestrianGateway
Indicates that something serves as an access point or entrance specifically intended for use by pedestrians.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681091fa08190afb11bbb118e1537 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:46 p.m.