Triple
T21205444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohmte |
E522564
|
entity |
| Predicate | roadSafetyPolicy |
P68802
|
FINISHED |
| Object | traffic calming through shared space design |
—
|
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: traffic calming through shared space design | Statement: [Bohmte, roadSafetyPolicy, traffic calming through shared space design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSafetyPolicy Context triple: [Bohmte, roadSafetyPolicy, traffic calming through shared space design]
-
A.
hasBicyclePolicy
Indicates that there exists a specific policy or set of rules governing the use, storage, or management of bicycles in relation to the subject.
-
B.
roadSide
Indicates that one entity is located along, beside, or immediately adjacent to a road.
-
C.
safetyConcept
chosen
Indicates that something embodies, represents, or is associated with a principle, idea, or framework related to safety.
-
D.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
E.
roadTrafficRuleJurisdiction
Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734342e9081909e241bed54dbc0b4 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:20 p.m.