Triple
T8741709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIBERIAN |
E207517
|
entity |
| Predicate | usedInServiceType |
P53961
|
FINISHED |
| Object | commercial 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: commercial aviation | Statement: [SIBERIAN, usedInServiceType, commercial aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInServiceType Context triple: [SIBERIAN, usedInServiceType, commercial aviation]
-
A.
usedForService
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
-
B.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
C.
appliesToServiceType
chosen
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
D.
usesServiceDesignation
Indicates that one entity adopts or applies a particular service designation associated with another entity or offering.
-
E.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d6fd5dc8190906b7147f27c5d46 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.