Triple

T19149263
Position Surface form Disambiguated ID Type / Status
Subject Alcombe E468759 entity
Predicate locatedIn P40 FINISHED
Object Minehead NE NERFINISHED

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: Minehead | Statement: [Alcombe, locatedIn, Minehead]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Minehead
Context triple: [Alcombe, locatedIn, Minehead]
  • A. Minehead chosen
    Minehead is a coastal town and popular seaside resort on the Bristol Channel in Somerset, England, known for its beach, harbour, and proximity to Exmoor National Park.
  • B. Torresdale
    Torresdale is a residential neighborhood in the far northeastern section of Philadelphia, Pennsylvania, known for its proximity to the Delaware River and suburban character.
  • C. Sandhead
    Sandhead is a small coastal village in Dumfries and Galloway, southwest Scotland, known for its long sandy beach along Luce Bay.
  • D. Mo Town
    Mo Town is an American Thoroughbred racehorse best known for winning the Grade 1 Hollywood Derby before retiring to stud.
  • E. Middlewood
    Middlewood is a locality served by the Yellow Route public transit line.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dd084ff48190ac0f8c46ee722629 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e97c42348190875a2f5b5bc0b99e completed April 20, 2026, 8:53 a.m.
Created at: April 10, 2026, 12:06 p.m.