Triple
T28249471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Air Lines |
E712274
|
entity |
| Predicate | servesContinentCount |
P79596
|
FINISHED |
| Object | 6 continents |
—
|
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: 6 continents | Statement: [Delta Air Lines, servesContinentCount, 6 continents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesContinentCount Context triple: [Delta Air Lines, servesContinentCount, 6 continents]
-
A.
alsoServesContinent
Indicates that an entity, in addition to its primary region or scope, provides services to or covers the specified continent.
-
B.
hasCountryServed
Indicates that a person or organization has provided service to, or performed duties on behalf of, a specified country.
-
C.
hasNumberOfContinentsWithOperations
chosen
Indicates the count of distinct continents in which an entity conducts operations.
-
D.
servesCountryConnections
Indicates that an entity provides or facilitates service connections between different countries.
-
E.
destinationCountryServed
Indicates that a given entity (such as a service, route, or provider) serves or operates to a specified destination country.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 27, 2026, 11:03 p.m.