Triple

T8647458
Position Surface form Disambiguated ID Type / Status
Subject Laughton, Sussex E205012 entity
Predicate hasCivilParish P2739 FINISHED
Object Laughton E655592 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: Laughton | Statement: [Laughton, Sussex, hasCivilParish, Laughton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laughton
Context triple: [Laughton, Sussex, hasCivilParish, Laughton]
  • A. Laughton chosen
    Laughton is an English surname most famously associated with the acclaimed 20th-century actor and director Charles Laughton.
  • B. Farnum
    Farnum is a locality within Providence County, Rhode Island, likely a small village or neighborhood rather than an incorporated city.
  • C. Hannington
    Hannington is a small rural village in Wiltshire, England, known for its traditional English countryside setting and historic character.
  • D. Hartley
    Hartley is an English-language surname of Old English origin, commonly associated with various notable figures across fields such as science, politics, and the arts.
  • E. Hartley
    Hartley is a small census-designated community located in Solano County, California.
  • 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_69ca834e56848190abb0eeaec9dedd32 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc48112b4881908901214f41b6bf71 completed March 31, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69ceccb8b91881908630f3e4c4461af4 completed April 2, 2026, 8:08 p.m.
Created at: March 30, 2026, 6:29 p.m.