Triple
T6605924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Ostkreuz |
E149116
|
entity |
| Predicate | majorReconstructionCompleted |
P13529
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Berlin Ostkreuz, majorReconstructionCompleted, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorReconstructionCompleted Context triple: [Berlin Ostkreuz, majorReconstructionCompleted, 2018]
-
A.
majorRebuildCompleted
chosen
Indicates that a significant reconstruction or overhaul of an entity has been fully completed.
-
B.
majorRebuilder
Indicates that an entity plays a primary or leading role in reconstructing, restoring, or significantly rebuilding another entity.
-
C.
majorConstruction
Indicates a relationship where a construction project is large-scale, significant, or of primary importance in scope, impact, or resources.
-
D.
largelyRebuilt
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
E.
reconstructedDuring
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:56 p.m.