Triple
T14517766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akasa Air |
E340567
|
entity |
| Predicate | fleetModernity |
P114557
|
FINISHED |
| Object | modern narrow-body fleet |
—
|
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: modern narrow-body fleet | Statement: [Akasa Air, fleetModernity, modern narrow-body fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetModernity Context triple: [Akasa Air, fleetModernity, modern narrow-body fleet]
-
A.
plannedArmament
Indicates that an entity has a specific weapon or set of weapons intended or scheduled to be equipped or deployed in the future.
-
B.
fleetIncludes
Indicates that a particular fleet contains or is composed of the specified entity or entities as its members.
-
C.
enemyMilitaryAsset
Indicates that one entity is a military asset belonging to or controlled by an enemy force relative to the other entity.
-
D.
isMilitaryAssetOf
Indicates that something functions as a military resource, equipment, or facility that belongs to, is controlled by, or is used by a particular entity.
-
E.
militaryTechnology
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6f50208190b687b505f5cd1aa2 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:22 a.m.