Triple
T17770729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breite Straße |
E443628
|
entity |
| Predicate | formerCityContext |
P128864
|
FINISHED |
| Object | former city of Cölln |
—
|
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: former city of Cölln | Statement: [Breite Straße, formerCityContext, former city of Cölln]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCityContext Context triple: [Breite Straße, formerCityContext, former city of Cölln]
-
A.
formerCity
Indicates that an entity was once recognized as a city but no longer holds that status.
-
B.
formerCityName
Indicates that an entity was previously known by a different city name in the past.
-
C.
cityPreviouslyLocatedIn
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
-
D.
previouslyContainedCity
Indicates that one location used to include a particular city within its boundaries or jurisdiction at some time in the past, but no longer does.
-
E.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485ff928481909fe32260ba57978f |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:11 a.m.