Triple
T21712104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haus Potsdamer Straße |
E535930
|
entity |
| Predicate | hasMapDepartment |
P145054
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Haus Potsdamer Straße, hasMapDepartment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapDepartment Context triple: [Haus Potsdamer Straße, hasMapDepartment, yes]
-
A.
hasMaps
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
B.
hasMapRoom
Indicates that an entity includes or provides access to a dedicated room or space used for displaying or working with maps.
-
C.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
-
D.
refersToDepartmentInRegion
Indicates that an entity is associated with, or makes reference to, a specific department located within a particular region.
-
E.
hasDepartmentForTransportCategory
Indicates that an entity is classified under a specific category defined by the Department for Transport.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb53450108190ba1c9e3cc3a0ab89 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:46 p.m.