Triple
T25715423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Tokyo |
E644848
|
entity |
| Predicate | isCargoRoute |
P42526
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [London–Tokyo, isCargoRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCargoRoute Context triple: [London–Tokyo, isCargoRoute, true]
-
A.
isOnFreightRoute
chosen
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
B.
isKeyFreightRoute
Indicates that a transportation route serves as a primary or strategically important corridor for moving freight.
-
C.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
D.
hasCargoRole
Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
-
E.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:40 p.m.