Triple
T26131276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rathausstraße (Berlin) |
E659252
|
entity |
| Predicate | hasHeritageBuildingAlong |
P48773
|
FINISHED |
| Object | Rotes Rathaus |
—
|
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: Rotes Rathaus | Statement: [Rathausstraße (Berlin), hasHeritageBuildingAlong, Rotes Rathaus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageBuildingAlong Context triple: [Rathausstraße (Berlin), hasHeritageBuildingAlong, Rotes Rathaus]
-
A.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
-
B.
hasHeritageListedPlace
chosen
Indicates that an entity possesses or is associated with a place that is officially designated as heritage-listed.
-
C.
hasReligiousBuildingAlong
Indicates that a religious building is located along the course, path, or extent of the referenced entity.
-
D.
hasHeritageElements
Indicates that something contains or includes elements that are part of a cultural, historical, or natural heritage.
-
E.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 8:15 p.m.