Triple

T7300111
Position Surface form Disambiguated ID Type / Status
Subject Vallorbe E167824 entity
Predicate hasRiver P165 FINISHED
Object Orbe E300456 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: Orbe | Statement: [Vallorbe, hasRiver, Orbe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orbe
Context triple: [Vallorbe, hasRiver, Orbe]
  • A. Orbe chosen
    The Orbe is a river in western Switzerland and eastern France that flows through the Jura region before joining the Aare river system.
  • B. Orbiel
    The Orbiel is a river in southern France that flows through the Aude department before joining the Aude River.
  • C. Oribos
    Oribos is the central hub city and afterlife crossroads in World of Warcraft: Shadowlands, where players gather, trade, and access the expansion’s various realms.
  • D. Oro
    Oro is an ethnic group indigenous to Nigeria’s Akwa Ibom State, known for its distinct language and coastal cultural heritage.
  • E. Ermera
    Ermera is a mountainous municipality in central Timor-Leste known for its coffee production and significant Mambae-speaking population.
  • 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_69c6888c820881909fc68f689fe1c251 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6ebaef4a081908fadc6d5e2621e80 completed March 27, 2026, 8:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7e554833c8190ac124421379639bd completed March 28, 2026, 2:27 p.m.
Created at: March 27, 2026, 3:01 p.m.