Triple
T8299045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narvik–Germany iron ore route |
E194297
|
entity |
| Predicate | cargoDestination |
P12202
|
FINISHED |
| Object | German North Sea ports |
—
|
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: German North Sea ports | Statement: [Narvik–Germany iron ore route, cargoDestination, German North Sea ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoDestination Context triple: [Narvik–Germany iron ore route, cargoDestination, German North Sea ports]
-
A.
cargo
chosen
Indicates that one entity is the goods or load being transported, carried, or shipped by another entity.
-
B.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
-
C.
transferDestination
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
D.
creatorMigrationDestination
Indicates the location or entity to which a creator moves or relocates as part of a migration process.
-
E.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7dfb60e48190bfa5de1c1496d3b5 |
completed | March 31, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.