Triple
T27324782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Hemswell |
E689611
|
entity |
| Predicate | closureUse |
P162187
|
FINISHED |
| Object | civilian use |
—
|
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: civilian use | Statement: [RAF Hemswell, closureUse, civilian use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureUse Context triple: [RAF Hemswell, closureUse, civilian use]
-
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.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
D.
closureAffected
Indicates that an entity is impacted or influenced by the closing or termination of another entity, process, or resource.
-
E.
closureContributesTo
Indicates that the existence or characteristics of a closure play a role in producing, enabling, or enhancing a particular outcome, state, or property.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627ed03ac8190a17ddacba96f8a48 |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:35 a.m.