Triple
T33595659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albertplatz |
E860556
|
entity |
| Predicate | isMajorTrafficJunctionOf |
P184542
|
FINISHED |
| Object | Dresden Neustadt |
—
|
NE NERFINISHED |
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: Dresden Neustadt | Statement: [Albertplatz, isMajorTrafficJunctionOf, Dresden Neustadt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTrafficJunctionOf Context triple: [Albertplatz, isMajorTrafficJunctionOf, Dresden Neustadt]
-
A.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
B.
atJunctionOf
chosen
Indicates that something is located at or directly connected to the point where two or more paths, roads, or lines meet.
-
C.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
D.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
E.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 1:41 a.m.