Triple

T5116784
Position Surface form Disambiguated ID Type / Status
Subject River Rhondda E115354 entity
Predicate flowsThrough P225 FINISHED
Object Ferndale E106696 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: Ferndale | Statement: [River Rhondda, flowsThrough, Ferndale]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ferndale
Context triple: [River Rhondda, flowsThrough, Ferndale]
  • A. Ferndale chosen
    Ferndale is a former coal-mining town and community located in the Rhondda Fach valley in south Wales.
  • B. Ferndale
    Ferndale is a small city in northwestern Washington State, known for its proximity to the Canadian border and the city of Bellingham.
  • C. Ferndale, Michigan
    Ferndale, Michigan is a small inner-ring Detroit suburb known for its vibrant downtown, progressive community, and active arts and LGBTQ+ scenes.
  • D. Galewood
    Galewood is a neighborhood on Chicago’s Northwest Side that is served by a station on Metra’s Milwaukee District West Line.
  • E. Fairview, Michigan
    Fairview, Michigan is a small unincorporated community in Oscoda County known as a rural service center amid the forests and lakes of northeastern Michigan’s Lower Peninsula.
  • 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_69bd4441d1648190a54a533895041987 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd75cfa9f88190aa7dfd264e554899 completed March 20, 2026, 4:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69bebaafd674819080b751216e5b6f70 completed March 21, 2026, 3:35 p.m.
Created at: March 20, 2026, 1:41 p.m.