Triple
T15545815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Airways |
E370604
|
entity |
| Predicate | routeNetworkScope |
P119124
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [British Airways, routeNetworkScope, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNetworkScope Context triple: [British Airways, routeNetworkScope, global]
-
A.
routingDomainScope
Indicates the specific routing domain or context within which a route, policy, or network configuration is valid or applied.
-
B.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
C.
routingCapability
Indicates the ability of an entity to determine and direct the path that data, messages, or items should take through a network or system.
-
D.
hasRouteNetwork
Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
-
E.
routingDomainType
Indicates the classification or category of routing domain associated with a given routing configuration or relationship.
- F. None of above. chosen
Provenance (4 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a9073948190b6e9cf504aacc7cf |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:07 a.m.