Triple
T20627650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic core of Guildford |
E506859
|
entity |
| Predicate | isPedestrianFocus |
P140829
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [historic core of Guildford, isPedestrianFocus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPedestrianFocus Context triple: [historic core of Guildford, isPedestrianFocus, true]
-
A.
hasPedestrianFunction
Indicates that an entity serves a role, purpose, or function specifically related to pedestrians or pedestrian use.
-
B.
isPedestrianHeavy
Indicates that an area, route, or location experiences a high volume or density of pedestrian traffic.
-
C.
isPedestrianGateway
Indicates that something serves as an access point or entrance specifically intended for use by pedestrians.
-
D.
hasPedestrianPriority
Indicates that pedestrians are given precedence or right-of-way over other road users in a particular context or area.
-
E.
hasPedestrianCharacter
Indicates that something possesses qualities, features, or behavior characteristic of pedestrians or pedestrian use.
- F. None of above. chosen
Provenance (4 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe645888190b639ebedc5b3041a |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.