Triple

T6665981
Position Surface form Disambiguated ID Type / Status
Subject River Ant E151603 entity
Predicate hasPart P35 FINISHED
Object Limekiln Dyke E476163 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: Limekiln Dyke | Statement: [River Ant, hasPart, Limekiln Dyke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Limekiln Dyke
Context triple: [River Ant, hasPart, Limekiln Dyke]
  • A. Washdyke
    Washdyke is a suburb and industrial area on the northern outskirts of Timaru in the South Island of New Zealand.
  • B. Devil’s Dyke
    Devil’s Dyke is a dramatic V-shaped dry valley and popular beauty spot in the South Downs near Brighton, known for its sweeping views, walking trails, and paragliding.
  • C. Oldcotes Dyke chosen
    Oldcotes Dyke is a small watercourse in Nottinghamshire, England, that serves as a minor tributary within the River Idle catchment.
  • D. Snake Dike
    Snake Dike is a classic, runout slab and dike rock climbing route on the southwest face of Half Dome in Yosemite National Park.
  • E. Offa's Dyke
    Offa's Dyke is a large early medieval earthwork running roughly along the England–Wales border, traditionally attributed to King Offa of Mercia as a defensive and territorial boundary.
  • 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_69c687f71fc081909dbd45d6377f6045 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b09d97648190a254cabc0ffcb0dc completed March 27, 2026, 4:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6ef0e33308190995fcccf50d134c1 completed March 27, 2026, 8:56 p.m.
Created at: March 27, 2026, 2:02 p.m.