Triple
T23943455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin B |
E602851
|
entity |
| Predicate | coversMunicipalArea |
P19200
|
FINISHED |
| Object | Berlin districts outside central A zone |
—
|
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: Berlin districts outside central A zone | Statement: [Berlin B, coversMunicipalArea, Berlin districts outside central A zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversMunicipalArea Context triple: [Berlin B, coversMunicipalArea, Berlin districts outside central A zone]
-
A.
hasMunicipalUnitArea
Indicates that a municipal unit is associated with a specific measured area.
-
B.
coversCity
Indicates that one entity extends over, includes, or geographically encompasses the area of a specified city.
-
C.
hasMunicipalAreaFeature
Indicates that a municipal area possesses or contains a specific geographic or infrastructural feature within its boundaries.
-
D.
regionCoverage
chosen
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
E.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02bf38081909c99b98e04a8d2aa |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:10 p.m.