Triple
T30918812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarkel |
E787660
|
entity |
| Predicate | controlsTradeRoute |
P171398
|
FINISHED |
| Object | Volga–Don portage |
—
|
NE NERFINISHED |
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: Volga–Don portage | Statement: [Sarkel, controlsTradeRoute, Volga–Don portage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsTradeRoute Context triple: [Sarkel, controlsTradeRoute, Volga–Don portage]
-
A.
includesTradeRoute
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
B.
controlledSeaRoute
chosen
Indicates that one entity has authority over, or the ability to regulate and manage access through, a particular maritime route used for navigation or transport.
-
C.
controlledTradeWith
Indicates a regulated or restricted trading relationship in which one entity manages, oversees, or limits the trade activities conducted with another entity.
-
D.
tradeAspect
Indicates a relationship where one entity is associated with a specific aspect, feature, or dimension of a trade or commercial transaction.
-
E.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 29, 2026, 8:51 p.m.