Triple
T21205428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohmte |
E522564
|
entity |
| Predicate | appliedTrafficConcept |
P17413
|
FINISHED |
| Object | shared space |
—
|
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: shared space | Statement: [Bohmte, appliedTrafficConcept, shared space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedTrafficConcept Context triple: [Bohmte, appliedTrafficConcept, shared space]
-
A.
traffics
Indicates engaging in the buying, selling, or illicit trading of someone or something, typically as part of an ongoing commercial or criminal operation.
-
B.
trafficManagementStrategy
chosen
Indicates a method or plan used to control, organize, or optimize the flow of traffic within a transportation system.
-
C.
trafficManagementGoal
Indicates a goal or objective related to managing, regulating, or optimizing traffic flow and conditions.
-
D.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
E.
facilitatesTrafficFlowBetween
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
- 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.