Triple
T25026076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QG |
E626710
|
entity |
| Predicate | airlineServiceScope |
P159407
|
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: [QG, airlineServiceScope, international flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineServiceScope Context triple: [QG, airlineServiceScope, international flights]
-
A.
airlineServiceScope
chosen
Indicates the range or extent of services an airline provides, such as which routes, regions, or markets it operates in.
-
B.
airlineGroupScope
Indicates that a relationship or action applies specifically within the context or boundaries of a particular airline group.
-
C.
airlineContext
Indicates a relationship, situation, or action that specifically occurs within or is constrained by an airline-related context (such as flights, carriers, or air travel operations).
-
D.
airlineAllianceScope
Indicates the extent or coverage of an airline alliance’s operations or cooperation (e.g., regional vs. global).
-
E.
airlineService
Indicates that an airline operates transportation services (such as flights) between specified locations or for specified routes.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:07 a.m.