Triple
T23555138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IL18 |
E578165
|
entity |
| Predicate | aircraftTypeOrigin |
P68259
|
FINISHED |
| Object | Soviet-era civil aviation |
—
|
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: Soviet-era civil aviation | Statement: [IL18, aircraftTypeOrigin, Soviet-era civil aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeOrigin Context triple: [IL18, aircraftTypeOrigin, Soviet-era civil aviation]
-
A.
aircraftOriginCountry
chosen
Indicates the country from which an aircraft originates, such as where it was built, registered, or primarily associated.
-
B.
usedAircraftOrigin
Indicates the place or source from which a used aircraft was originally obtained or came.
-
C.
airlineConfigurationOrigin
Indicates the original source or starting point from which a particular airline configuration was created or derived.
-
D.
appliedToAircraftBuiltBy
Indicates that something (such as a regulation, modification, or action) is applied specifically to aircraft that were built by a particular manufacturer or builder.
-
E.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed253788190ba75109af0e91b37 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:12 p.m.