Triple

T1186661
Position Surface form Disambiguated ID Type / Status
Subject Maas E25262 entity
Predicate tributary P415 FINISHED
Object Ourthe E118855 NE 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: Ourthe | Statement: [Maas, tributary, Ourthe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ourthe
Context triple: [Maas, tributary, Ourthe]
  • A. Ourthe chosen
    The Ourthe is a scenic river in southeastern Belgium that flows through the Ardennes region, known for its winding valleys, outdoor recreation, and picturesque towns.
  • B. Wem
    Wem is a small market town and civil parish in the county of Shropshire, England.
  • C. Hyllus
    Hyllus is a figure in Greek mythology known as the son of Heracles and Deianira, often associated with the Dorian invasion and the Heracleidae.
  • D. Garthdee
    Garthdee is a riverside area in the southwest of Aberdeen, Scotland, known for hosting the main campus of Robert Gordon University.
  • E. Golus
    Golus is a Yiddish term referring to the Jewish exile and dispersion from their ancestral homeland, encompassing both the physical diaspora and its spiritual-historical implications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a49427d98881908646d6c63b8cea1e completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd5578b08190bbe4089857fbf166 completed March 1, 2026, 10:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac6f239a288190ae488d11cff8ebf2 completed March 7, 2026, 6:32 p.m.
Created at: March 1, 2026, 7:45 p.m.