Triple
T28184121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC |
E716120
|
entity |
| Predicate | airlineAlsoOperates |
P116296
|
FINISHED |
| Object | international flights |
—
|
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: international flights | Statement: [BC, airlineAlsoOperates, international flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineAlsoOperates Context triple: [BC, airlineAlsoOperates, international flights]
-
A.
usedByAirlineAlsoKnownAs
Indicates that an item (such as a code, name, or identifier) is used by an airline that is also known by an alternative name.
-
B.
airlineOperator
Indicates that one entity operates or manages airline services for another entity or in a specified context.
-
C.
aircraftOperator
Indicates that one entity operates, manages, or is responsible for the use of a particular aircraft.
-
D.
airTransportServedBy
chosen
Indicates that a particular air transport service (such as a route, flight, or airport operation) is provided or operated by a specified carrier or service provider.
-
E.
airLegOperatedBy
Indicates that a specific segment (leg) of an air journey is operated by a particular airline or 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 10:21 p.m.