Triple

T15130335
Position Surface form Disambiguated ID Type / Status
Subject Dacorum E361400 entity
Predicate borderedBy P224 FINISHED
Object Three Rivers E627534 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: Three Rivers | Statement: [Dacorum, borderedBy, Three Rivers]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Three Rivers
Context triple: [Dacorum, borderedBy, Three Rivers]
  • A. Three Rivers
    Three Rivers was an Amtrak long-distance passenger train that operated between New York City and Chicago via Pittsburgh.
  • B. Three Rivers
    Three Rivers is a hamlet in central New York known as the junction where the Seneca, Oneida, and Oswego rivers meet.
  • C. Three Rivers
    Three Rivers is a small gateway community in California’s Sierra Nevada foothills, known as an access point to Sequoia and Kings Canyon National Parks.
  • D. Three Rivers chosen
    Three Rivers is a local government district in Hertfordshire, England, named after the rivers Gade, Chess, and Colne that run through it.
  • E. Three Rivers
    Three Rivers is a village within the town of Palmer, Massachusetts, known historically as a mill and industrial community at the confluence of three rivers.
  • 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_69d85a06450081909c5a14ea9851a15e completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e005b194748190801e3956bf2429d4 completed April 15, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69feb7fa449c8190aed8941168b063c3 completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 3:06 a.m.