Triple
T37966822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Laarbruch |
E947166
|
entity |
| Predicate | postClosureName |
P189817
|
FINISHED |
| Object | Weeze Airport |
—
|
NE NERFINISHED |
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: Weeze Airport | Statement: [RAF Laarbruch, postClosureName, Weeze Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postClosureName Context triple: [RAF Laarbruch, postClosureName, Weeze Airport]
-
A.
postClosureOperator
Indicates that one entity functions as a closure-like operator applied after another operation or process, producing a resulting state or outcome.
-
B.
postClosureRedevelopedAs
Indicates that after an entity has closed or ceased operation, it is subsequently redeveloped or repurposed into another form or use.
-
C.
postClosureActivity
Indicates activities or processes that occur after the formal completion or closure of an event, project, or case.
-
D.
postClosurePlanning
Indicates the planning activities and arrangements that are carried out after the formal closure of a project, process, or event.
-
E.
postClosureAuthority
Indicates that an entity has the authority or responsibility to act, decide, or manage matters after a specified closure event or period.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.