Triple
T28724310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmarkt (Dresden) |
E730179
|
entity |
| Predicate | locatedInTheStreetSystemOf |
P200661
|
FINISHED |
| Object | Altmarkt area |
—
|
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: Altmarkt area | Statement: [Altmarkt (Dresden), locatedInTheStreetSystemOf, Altmarkt area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTheStreetSystemOf Context triple: [Altmarkt (Dresden), locatedInTheStreetSystemOf, Altmarkt area]
-
A.
takesPlaceOnStreets
Indicates that an event or activity occurs in or along streets as its primary location.
-
B.
locatedBetweenStreets
Indicates that something is situated between two specified streets, with its position bounded or defined by those streets.
-
C.
sitsOnStreet
Indicates that an entity is located or positioned directly on a street surface.
-
D.
isPartOfStreetscape
Indicates that something forms a component or element within the overall layout or visual composition of a streetscape.
-
E.
cityStreetUsed
Indicates that a particular city street is utilized or traversed in the course of some activity, route, or event.
- F. None of above. chosen
Provenance (4 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: April 28, 2026, 5:55 a.m.