Triple
T17481170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas Air |
E425661
|
entity |
| Predicate | operatesOnRouteType |
P13326
|
FINISHED |
| Object | intercontinental routes |
—
|
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: intercontinental routes | Statement: [Atlas Air, operatesOnRouteType, intercontinental routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnRouteType Context triple: [Atlas Air, operatesOnRouteType, intercontinental routes]
-
A.
operatedOnRoute
Indicates that a transportation service or vehicle was active and provided service along a specified route.
-
B.
operatesOnRouteSection
Indicates that an entity performs its function or service along, within, or in connection with a specific route section.
-
C.
hasRouteType
chosen
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
D.
operatedRoutes
Indicates that an agent (such as a company or organization) runs or manages specific routes, typically providing services along those paths.
-
E.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bfd75481908c20bc2c1cbff593 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.