Triple

T5901707
Position Surface form Disambiguated ID Type / Status
Subject Hartley E131240 entity
Predicate hasVariant P455 FINISHED
Object Hartly E131240 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: Hartly | Statement: [Hartley, hasVariant, Hartly]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hartly
Context triple: [Hartley, hasVariant, Hartly]
  • A. Hartley
    Hartley is a small census-designated community located in Solano County, California.
  • B. Hartley chosen
    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.
  • C. Hayle
    Hayle is a small coastal town and port in west Cornwall, England, situated at the mouth of the Hayle River and known for its industrial heritage and sandy beaches.
  • D. Heseltine
    Heseltine is a surname most prominently associated with Michael Heseltine, a senior British Conservative politician and former Deputy Prime Minister.
  • E. Tattersett
    Tattersett is a small village and civil parish in Norfolk, England, situated in a rural area of the county.
  • 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_69c0085864a88190a569c05ff7d65f29 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0373489208190ba51c013e81c9938 completed March 22, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b16297588190928693a7c31ec0a7 completed March 23, 2026, 3:20 a.m.
Created at: March 22, 2026, 3:58 p.m.