Triple
T22697006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamchatka Aviation Enterprise |
E561206
|
entity |
| Predicate | fleetUsage |
P103586
|
FINISHED |
| Object | short-haul routes |
—
|
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: short-haul routes | Statement: [Kamchatka Aviation Enterprise, fleetUsage, short-haul routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetUsage Context triple: [Kamchatka Aviation Enterprise, fleetUsage, short-haul routes]
-
A.
fleetPurpose
chosen
Indicates the primary function, role, or intended use of a fleet within a given context.
-
B.
usesFleetOf
Indicates that one entity operates or relies on a group of vehicles, vessels, or similar assets collectively as a fleet to perform its activities or services.
-
C.
fleetIncludes
Indicates that a particular fleet contains or is composed of the specified entity or entities as its members.
-
D.
fleetNumbers
Indicates that there is an association between an entity and one or more identifying numbers assigned to it as part of a fleet.
-
E.
fleetCondition
Indicates the overall operational status or state of readiness of a group of vehicles, vessels, or similar assets considered as a fleet.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789f26848190bcc5a99e3ed909e7 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.