Triple

T12489422
Position Surface form Disambiguated ID Type / Status
Subject Connolly E298522 entity
Predicate hasVariant P455 FINISHED
Object Conolly E658007 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: Conolly | Statement: [Connolly, hasVariant, Conolly]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Conolly
Context triple: [Connolly, hasVariant, Conolly]
  • A. Conolly chosen
    Conolly is a surname most notably associated with Arthur Conolly, a 19th-century British intelligence officer and explorer involved in the "Great Game" in Central Asia.
  • B. Earnley
    Earnley is a small rural village and civil parish in West Sussex, England, situated near the south coast on the Manhood Peninsula.
  • C. Credenhill
    Credenhill is a village in Herefordshire, England, known for its rural setting and proximity to military facilities such as Stirling Lines.
  • D. Stonely
    Stonely is a small village in Cambridgeshire, England, situated close to the town of Kimbolton.
  • E. Fairlop
    Fairlop is a suburban area in northeast London known for its open green spaces, including Fairlop Waters Country Park and its large lake.
  • 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_69d6ada377208190a36011199a4d8558 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94de1db9481909ddf70eb81cdb714 completed April 10, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64ba9e1108190b74984d9da9baebe completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:56 p.m.