Triple
T3381748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Brandenburg Airport |
E71200
|
entity |
| Predicate | projectDelays |
P33636
|
FINISHED |
| Object | multiple opening postponements |
—
|
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: multiple opening postponements | Statement: [Berlin Brandenburg Airport, projectDelays, multiple opening postponements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectDelays Context triple: [Berlin Brandenburg Airport, projectDelays, multiple opening postponements]
-
A.
projectOutcome
Indicates the resulting state, impact, or consequences produced by carrying out a project.
-
B.
project
Indicates that an entity plans, organizes, or carries out a structured effort or initiative aimed at achieving a specific goal or outcome.
-
C.
overseesProject
Indicates that one entity has responsibility for supervising, managing, or directing the progress and execution of a project involving another entity.
-
D.
endedDueTo
Indicates that an event, process, or state came to a conclusion specifically because of a particular cause or condition.
-
E.
projectFaced
chosen
Indicates that a project encountered or experienced specific challenges, obstacles, or conditions during its course.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e9af608190bfb228ef99a87bb7 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.