Triple
T3721140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werderscher Markt 1, Berlin |
E81639
|
entity |
| Predicate | cityDistrictFunction |
P51431
|
FINISHED |
| Object | federal government site |
—
|
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: federal government site | Statement: [Werderscher Markt 1, Berlin, cityDistrictFunction, federal government site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDistrictFunction Context triple: [Werderscher Markt 1, Berlin, cityDistrictFunction, federal government site]
-
A.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
-
B.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
C.
cityDistrictLevel
Indicates that one administrative unit is a district-level subdivision within a given city in the territorial hierarchy.
-
D.
endPointDistrict
Indicates the district in which a path, route, or connection terminates.
-
E.
majorCityInDistrict
Indicates that a city serves as a major or principal urban center within a specified district.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9d29208190bbf38a6aa88f954a |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc48ec1a081909af0ff9f267c0ffe |
completed | March 8, 2026, 6:48 p.m. |
Created at: March 8, 2026, 3:34 p.m.