Triple
T14379929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wendover Army Air Field |
E356572
|
entity |
| Predicate | laterPartiallyConvertedTo |
P91350
|
FINISHED |
| Object | civil 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: civil airport | Statement: [Wendover Army Air Field, laterPartiallyConvertedTo, civil airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPartiallyConvertedTo Context triple: [Wendover Army Air Field, laterPartiallyConvertedTo, civil airport]
-
A.
partlyUpgradedTo
Indicates that an entity has undergone an incomplete or partial upgrade to another specified state, version, or configuration.
-
B.
someConvertedTo
chosen
Indicates that a portion of one entity has been transformed or changed into another entity.
-
C.
partiallyCompleted
Indicates that an action, process, or task has been started and progressed to some extent, but has not yet been fully completed.
-
D.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
E.
partiallyIncorporatedInto
Indicates that one entity has been integrated or absorbed into another entity, but only to a limited or incomplete extent.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900bbfb08190a1e56f281a2374c0 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.