Triple
T26365772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spreepark |
E660326
|
entity |
| Predicate | municipalDistrict |
P78738
|
FINISHED |
| Object | Treptow-Köpenick |
—
|
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: Treptow-Köpenick | Statement: [Spreepark, municipalDistrict, Treptow-Köpenick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalDistrict Context triple: [Spreepark, municipalDistrict, Treptow-Köpenick]
-
A.
governmentalDistrictOf
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
-
B.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
C.
hasMunicipalDistrict
chosen
Indicates that an administrative entity includes or is divided into one or more municipal districts as its subordinate units.
-
D.
district
Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
-
E.
municipalCountrySubdivision
Indicates that one administrative area functions as a municipal-level subdivision within the territory of a given country.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6102c248c8190886da68d61d006dc |
completed | May 2, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:54 p.m.