Triple
T17895116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian broad-gauge network |
E447412
|
entity |
| Predicate | borderCrossingTechnique |
P72797
|
FINISHED |
| Object | transshipment of freight |
—
|
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: transshipment of freight | Statement: [Russian broad-gauge network, borderCrossingTechnique, transshipment of freight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingTechnique Context triple: [Russian broad-gauge network, borderCrossingTechnique, transshipment of freight]
-
A.
borderCrossingMode
chosen
Indicates the means or method by which a border is crossed between territories or jurisdictions.
-
B.
borderCrossingStatus
Indicates the current state or outcome of an entity’s attempt to cross a border (e.g., allowed, denied, pending, or completed).
-
C.
borderCrossingArea
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
-
D.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
E.
borderCrossingRequirement
Indicates the conditions or obligations that must be met for an entity to legally or formally cross a border between jurisdictions.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7eb4f48190951e26975b57873b |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.