Triple
T23892575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meigs Field |
E600811
|
entity |
| Predicate | closureAction |
P19866
|
FINISHED |
| Object | runway destroyed overnight by city order |
—
|
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: runway destroyed overnight by city order | Statement: [Meigs Field, closureAction, runway destroyed overnight by city order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureAction Context triple: [Meigs Field, closureAction, runway destroyed overnight by city order]
-
A.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
B.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
C.
closureEvent
chosen
Indicates an event or action in which something is formally brought to an end, completed, or shut down.
-
D.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
E.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cd044708819091102ecc160e1961 |
completed | April 29, 2026, 9:19 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.