Triple
T37173277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glomma river region |
E920970
|
entity |
| Predicate | historicallyReliedOn |
P140658
|
FINISHED |
| Object | river transport |
—
|
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: river transport | Statement: [Glomma river region, historicallyReliedOn, river transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyReliedOn Context triple: [Glomma river region, historicallyReliedOn, river transport]
-
A.
isHistoricallyDependentOn
chosen
Indicates that one entity’s existence, development, or validity is contingent on prior events, conditions, or states associated with another entity in history.
-
B.
historicallyBackedBy
Indicates that something is supported, justified, or validated by historical evidence, records, or precedent.
-
C.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
D.
historicallyReplaced
Indicates that one entity took the place of another in fulfilling a similar role or function at some point in history.
-
E.
historicallyExtendedBy
Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
Created at: May 3, 2026, 4:15 p.m.