Triple

T17846619
Position Surface form Disambiguated ID Type / Status
Subject Kfar Saba E445678 entity
Predicate locatedIn P40 FINISHED
Object Sharon plain E484960 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: Sharon plain | Statement: [Kfar Saba, locatedIn, Sharon plain]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sharon plain
Context triple: [Kfar Saba, locatedIn, Sharon plain]
  • A. Sharon plain chosen
    Sharon plain is a fertile coastal region in central Israel known historically for its agriculture and ancient settlements.
  • B. New Sharon
    New Sharon is a small rural city located in central Iowa, United States.
  • C. Sharon Heights
    Sharon Heights is an affluent residential neighborhood in Menlo Park, California, known for its upscale homes, golf course, and proximity to Silicon Valley.
  • D. Sholden
    Sholden is a small village and civil parish in Kent, England, situated near the coastal town of Deal.
  • E. Shannons Flat
    Shannons Flat is a rural locality in the Snowy Monaro region of New South Wales, Australia, known for its high-country landscapes and proximity to the Snowy Mountains.
  • 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ffb35248190a80a428686e06d87 completed April 19, 2026, 8:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a030c5c53b88190bd641a310ad29923 completed May 12, 2026, 11:17 a.m.
Created at: April 10, 2026, 10:16 a.m.