Triple
T33647736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DREAMJET |
E862006
|
entity |
| Predicate | associatedWithRouteType |
—
|
GENERATED |
| Object | transatlantic flights |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRouteType Context triple: [DREAMJET, associatedWithRouteType, transatlantic flights]
-
A.
associatedWithRouteNetwork
Indicates a relationship where something is linked or connected to a specific route network.
-
B.
hasRouteType
chosen
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
C.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
D.
associatedWithDirection
Indicates that something has a relationship to, or is characterized by, a particular spatial or directional orientation.
-
E.
associatedWithRule
Indicates that an entity is linked or connected to a specific rule, such as being governed, constrained, or defined by that rule.
- F. None of above.
Provenance (1 batch)
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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.