Triple
T2334702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smartavia |
E44282
|
entity |
| Predicate | operatesAircraftCategory |
P1524
|
FINISHED |
| Object | narrow-body jet |
—
|
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: narrow-body jet | Statement: [Smartavia, operatesAircraftCategory, narrow-body jet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAircraftCategory Context triple: [Smartavia, operatesAircraftCategory, narrow-body jet]
-
A.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
usedByAircraftType
Indicates that something (such as equipment, infrastructure, or a procedure) is employed or operated by a specific type or category of aircraft.
-
C.
canOperateHelicopterType
Indicates that one entity has the ability, qualification, or authorization to operate or pilot a specified type of helicopter.
-
D.
usesCarrierAircraft
Indicates that one entity employs or operates aircraft that are designed to be launched from and recovered by an aircraft carrier.
-
E.
carrierAircraft
Indicates that an aircraft is designed, equipped, or used to operate from an aircraft carrier.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.