Triple

T17807817
Position Surface form Disambiguated ID Type / Status
Subject City of Glarus E444612 entity
Predicate hasRiver P165 FINISHED
Object Linth 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: Linth | Statement: [City of Glarus, hasRiver, Linth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Linth
Context triple: [City of Glarus, hasRiver, Linth]
  • A. Linth chosen
    The Linth is a major river in eastern Switzerland that flows through the canton of Glarus before joining the Rhine.
  • B. Terling
    Terling is a small rural village and civil parish in the county of Essex in eastern England, known for its historic buildings and countryside setting.
  • C. Tealing
    Tealing is a small rural village in eastern Scotland, situated in the Angus council area just north of Dundee.
  • D. Linnton
    Linnton is a riverside neighborhood in northwest Portland, Oregon, characterized by its mix of industrial areas, forested hillsides, and access to the Willamette River.
  • E. Tesseney
    Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9efe370819095cd219b143ae727 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e488779a3081908405eac4930a095f completed April 19, 2026, 7:47 a.m.
Created at: April 10, 2026, 10:14 a.m.