Triple
T4223074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIR |
E94387
|
entity |
| Predicate | airlineTypeIdentified |
P15154
|
FINISHED |
| Object | scheduled passenger airline |
—
|
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: scheduled passenger airline | Statement: [VIR, airlineTypeIdentified, scheduled passenger airline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineTypeIdentified Context triple: [VIR, airlineTypeIdentified, scheduled passenger airline]
-
A.
airlineType
chosen
Indicates the classification or category of an airline based on its operational or service characteristics.
-
B.
servesAirlineType
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
C.
airlineCategory
Indicates the classification or type of an airline within a defined categorization system (e.g., full-service, low-cost, regional).
-
D.
airlineBrand
Indicates that one entity functions as the commercial airline brand associated with, or operating under, another entity.
-
E.
iataAircraftTypeCode
Indicates the standardized IATA code that specifies the aircraft type used in a flight or aviation context.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.