Triple
T770329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandenburg Gate |
E16265
|
entity |
| Predicate | carTraffic |
P4588
|
FINISHED |
| Object | closed to regular motor traffic |
—
|
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: closed to regular motor traffic | Statement: [Brandenburg Gate, carTraffic, closed to regular motor traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carTraffic Context triple: [Brandenburg Gate, carTraffic, closed to regular motor traffic]
-
A.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
B.
trafficLevel
chosen
Indicates the degree of congestion or flow intensity present in a transportation network or route at a given time.
-
C.
annualTraffic
Indicates the typical amount or volume of traffic associated with something over the course of a year.
-
D.
passengerTraffic
Indicates the flow or volume of passengers moving through or using a particular transport service, route, or facility.
-
E.
roadwayCarries
Indicates that a roadway serves as a route that supports or conveys a particular transportation facility, traffic flow, or designated use.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a704fb148190b203a5bdd77e961c |
completed | March 1, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.