Triple
T23409921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst-Reuter-Platz |
E560037
|
entity |
| Predicate | inUseAsTrafficCircle |
P143832
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Ernst-Reuter-Platz, inUseAsTrafficCircle, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUseAsTrafficCircle Context triple: [Ernst-Reuter-Platz, inUseAsTrafficCircle, 20th century]
-
A.
turningCircle
Indicates the radius or size of the circular path an object follows when it turns, typically reflecting how tightly it can change direction.
-
B.
hasTrafficIsland
Indicates the presence of a traffic island separating or organizing lanes or directions of vehicular movement within a roadway.
-
C.
hasRoundabout
chosen
Indicates that one location or roadway segment includes or is connected by a roundabout at or near that point.
-
D.
hasCircle
Indicates that one entity possesses, contains, or includes a circle as part of its structure or composition.
-
E.
hasRingRoadRole
Indicates that an entity has a specific functional role or responsibility in relation to a ring road.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a510b3848190ae42679ef0bcd424 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.