Triple

T4551996
Position Surface form Disambiguated ID Type / Status
Subject G. H. Hardy E120385 entity
Predicate hasSurname P18 FINISHED
Object Hardy E120385 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: Hardy | Statement: [G. H. Hardy, hasSurname, Hardy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hardy
Context triple: [G. H. Hardy, hasSurname, Hardy]
  • A. Hardy chosen
    Hardy is a surname most famously associated with the English mathematician G. H. Hardy, known for his contributions to number theory and mathematical analysis.
  • B. Louis Thomas Hardy
    Louis Thomas Hardy is the eldest son of English actor Tom Hardy.
  • C. J. F. Hardy
    J. F. Hardy was a mountaineer known for participating in the first recorded ascent of the Alpine peak Liskamm.
  • D. Edward Thomas Hardy
    Edward Thomas Hardy is an English actor and producer known for his intense, transformative performances in films such as Inception, Mad Max: Fury Road, and The Dark Knight Rises, as well as the TV series Peaky Blinders.
  • E. Ted Hardie
    Ted Hardie is an Internet engineering expert and long-time IETF leader known for his work on real-time communications and web technologies.
  • 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_69bd4636f1648190a701445c2fcd9c17 completed March 20, 2026, 1:05 p.m.
NER Named-entity recognition batch_69bd57f7b9748190af29d02fc77b02e0 completed March 20, 2026, 2:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdb95b01b0819094a600752e41aa09 completed March 20, 2026, 9:17 p.m.
Created at: March 20, 2026, 1:09 p.m.