Triple
T26131266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rathausstraße (Berlin) |
E659252
|
entity |
| Predicate | hasNearbyPublicSquare |
P7888
|
FINISHED |
| Object | Alexanderplatz |
E136235
|
NE 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: Alexanderplatz | Statement: [Rathausstraße (Berlin), hasNearbyPublicSquare, Alexanderplatz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyPublicSquare Context triple: [Rathausstraße (Berlin), hasNearbyPublicSquare, Alexanderplatz]
-
A.
hasNearbySquare
chosen
Indicates that one entity has at least one square-shaped entity located close to it in space.
-
B.
hasPublicSquareInFront
Indicates that a building or structure has a public square located directly in front of it.
-
C.
hasNearbyParkEntrance
Indicates that one location is situated close to an entrance of a park.
-
D.
hasNearbyCivicBuilding
Indicates that one entity is located close to, or in the immediate vicinity of, a civic building such as a government, public service, or community facility.
-
E.
hasAdjacentPlaza
Indicates that one place or structure is directly next to or bordering a plaza.
- F. None of above.
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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a118f96b900819091ac0262af96ea86 |
completed | May 23, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 26, 2026, 8:15 p.m.