Triple
T30257886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrichsfelde |
E769402
|
entity |
| Predicate | hasUrbanDistrictNumber |
P169381
|
FINISHED |
| Object | Ortsteil 1105 |
—
|
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: Ortsteil 1105 | Statement: [Friedrichsfelde, hasUrbanDistrictNumber, Ortsteil 1105]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanDistrictNumber Context triple: [Friedrichsfelde, hasUrbanDistrictNumber, Ortsteil 1105]
-
A.
hasUrbanDistrictCount
Indicates the number of urban districts associated with a given entity.
-
B.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
C.
hasUrbanDistrictFunction
Indicates that an entity serves the administrative or functional role of an urban district within a larger territorial or governance structure.
-
D.
hasUrbanDistrictStatusSince
Indicates that an entity has held the legal or administrative status of an urban district continuously since a specified point in time.
-
E.
isOneOfUrbanDistrictsOf
Indicates that an entity is a member of the set of urban districts belonging to a specified larger administrative area or city.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680a657bc8190b45a69e277bf5c6f |
completed | May 2, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:41 p.m.