Triple
T5782132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Tempelhof Airport |
E128182
|
entity |
| Predicate | terminalBuildingCompleted |
P65805
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Berlin Tempelhof Airport, terminalBuildingCompleted, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalBuildingCompleted Context triple: [Berlin Tempelhof Airport, terminalBuildingCompleted, 1941]
-
A.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
B.
towerCompleted
Indicates that the construction of a tower has been fully finished and reached its intended completed state.
-
C.
towerCompletedBefore
Indicates that the construction or completion of one tower occurred earlier in time than the construction or completion of another tower.
-
D.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
-
E.
hasTerminalBuildings
Indicates that one entity possesses or includes terminal buildings associated with it.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a17315881908aa12a830ba5f22b |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c024861bc88190a17782c1982fbb3e |
completed | March 22, 2026, 5:19 p.m. |
Created at: March 22, 2026, 3:50 p.m.