Triple
T30897138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khodynka Field |
E787050
|
entity |
| Predicate | airfieldClosureApproxDate |
P61288
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Khodynka Field, airfieldClosureApproxDate, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airfieldClosureApproxDate Context triple: [Khodynka Field, airfieldClosureApproxDate, late 20th century]
-
A.
airfieldOpened
Indicates that an airfield began operations or was officially opened at a certain time.
-
B.
airfieldDecommissioned
chosen
Indicates that an airfield has been officially taken out of service and is no longer used for regular aviation operations.
-
C.
closedForFlightOperations
Indicates that a location, facility, or area is temporarily unavailable or prohibited for conducting flight operations.
-
D.
airportOpened
Indicates that an airport began operations or was officially opened at a specific time.
-
E.
timePeriodOfFormerAirportUse
Indicates the span of time during which a location previously functioned as an airport before ceasing airport operations.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:49 p.m.