Triple
T986809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian Corridor |
E21296
|
entity |
| Predicate | otherMainRoute |
P19868
|
FINISHED |
| Object | Arctic convoys to Murmansk and Archangel |
—
|
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: Arctic convoys to Murmansk and Archangel | Statement: [Persian Corridor, otherMainRoute, Arctic convoys to Murmansk and Archangel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherMainRoute Context triple: [Persian Corridor, otherMainRoute, Arctic convoys to Murmansk and Archangel]
-
A.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
B.
otherMainBridge
Indicates that one bridge serves as an alternative or secondary primary bridge in relation to another main bridge.
-
C.
parentRoute
Indicates that one route serves as the direct hierarchical ancestor or container of another route within a routing structure.
-
D.
nextRoute
Indicates that one route directly follows another in a defined sequence or ordering of routes.
-
E.
alternativeRoute
chosen
Indicates that there exists a different path or option that can be taken instead of the primary or original route.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4a7754c8190a10ba0587bd8323d |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2abccbc8190a83af432f89eacf5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.