Triple

T27135742
Position Surface form Disambiguated ID Type / Status
Subject Tornedalen culture E681680 entity
Predicate hasCoreRiver P165 FINISHED
Object Torne River 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: Torne River | Statement: [Tornedalen culture, hasCoreRiver, Torne River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCoreRiver
Context triple: [Tornedalen culture, hasCoreRiver, Torne River]
  • A. hasRiver chosen
    Indicates that a location or area contains, is traversed by, or is directly associated with a river.
  • B. hasAncestralRiver
    Indicates that an entity is associated with or originates from a river regarded as its ancestral or traditional source.
  • C. hasMajorCityOnRiver
    Indicates that a major city is located on and directly associated with a particular river.
  • D. hasCityOnRiver
    Indicates that a city is located on or along the course of a particular river.
  • E. hasSettlementOnRiver
    Indicates that a settlement is located on or directly adjacent to a specific river.
  • 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_69eefacbcc2081909ebf00daa23f1981 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69fec8aef1d8819094c7fd7074038e6b completed May 9, 2026, 5:39 a.m.
PD Predicate disambiguation batch_69fec639876481908efd84a3631a4271 completed May 9, 2026, 5:29 a.m.
Created at: April 27, 2026, 9:07 a.m.