Triple
T30897136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khodynka Field |
E787050
|
entity |
| Predicate | airfieldAlsoKnownAs |
P170281
|
FINISHED |
| Object | Central Moscow Aerodrome |
—
|
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: Central Moscow Aerodrome | Statement: [Khodynka Field, airfieldAlsoKnownAs, Central Moscow Aerodrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airfieldAlsoKnownAs Context triple: [Khodynka Field, airfieldAlsoKnownAs, Central Moscow Aerodrome]
-
A.
airfieldUsedDuring
Indicates that an airfield was in operational use during a specified time period or event.
-
B.
relatedAirfield
Indicates that there is an association or connection between an entity and a specific airfield, such as operational use, location, or administrative linkage.
-
C.
airfieldCode
Indicates that an entity is identified by a specific airfield code used to uniquely reference that airfield.
-
D.
containsAirfield
Indicates that a location or area includes at least one airfield within its boundaries.
-
E.
airfieldBuilt
Indicates that an airfield has been constructed or established, typically specifying who built it, where, and/or when.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923c906c81908450147ba40dfeec |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:49 p.m.