Triple
T9083691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nollendorfplatz U-Bahn station |
E217695
|
entity |
| Predicate | hasRebuiltStructure |
P27798
|
FINISHED |
| Object | post-World War II reconstruction |
—
|
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: post-World War II reconstruction | Statement: [Nollendorfplatz U-Bahn station, hasRebuiltStructure, post-World War II reconstruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRebuiltStructure Context triple: [Nollendorfplatz U-Bahn station, hasRebuiltStructure, post-World War II reconstruction]
-
A.
hasRebuilt
Indicates that an entity has restored, reconstructed, or built again something that previously existed or was damaged or destroyed.
-
B.
hasRebuiltDate
Indicates the date on which something was rebuilt or reconstructed.
-
C.
hasReconstructedSite
chosen
Indicates that an entity has a site or location that has been rebuilt or restored after damage, destruction, or alteration.
-
D.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
E.
notRebuiltAfter
Indicates that an entity was destroyed or damaged and has not been reconstructed or restored after a specified event or point in time.
- 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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc960b45fc8190adf4bdc41b103e86 |
completed | April 1, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:13 p.m.