Triple
T568707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TXL |
E13614
|
entity |
| Predicate | closureRelatedTo |
P37
|
FINISHED |
| Object | opening of Berlin Brandenburg Airport |
—
|
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: opening of Berlin Brandenburg Airport | Statement: [TXL, closureRelatedTo, opening of Berlin Brandenburg Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureRelatedTo Context triple: [TXL, closureRelatedTo, opening of Berlin Brandenburg Airport]
-
A.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
B.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
closureAnnouncedBy
Indicates that an entity’s closure has been formally communicated or declared by a specified agent or source.
-
D.
relatedCase
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
-
E.
closedIn
Indicates that one entity is enclosed, contained, or surrounded within the boundaries or limits defined by another entity.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b0406d481908af5fc7bc67103fb |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c2caac819086ab316fa49d324c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.