Triple
T25966132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debis |
E645673
|
entity |
| Predicate | roleInPotsdamerPlatz |
P180294
|
FINISHED |
| Object | major developer |
—
|
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: major developer | Statement: [Debis, roleInPotsdamerPlatz, major developer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPotsdamerPlatz Context triple: [Debis, roleInPotsdamerPlatz, major developer]
-
A.
sideOfBerlin
Indicates a spatial or political relationship specifying on which side or sector of Berlin an entity is located or associated.
-
B.
partOfFormerEastBerlin
Indicates that the subject is located within the area that historically constituted East Berlin before German reunification.
-
C.
roleInBerlinOperation
Indicates that one entity participated in the Berlin operation with a specific role or function in relation to another entity or the operation itself.
-
D.
locatedInFormerWestOrEastBerlin
Indicates that the subject is located within an area that was part of either former West Berlin or former East Berlin before German reunification.
-
E.
sectionAtBerlin
Indicates that a section or segment of something is located in or associated with Berlin.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 22, 2026, 8:48 a.m.