Triple

T4089903
Position Surface form Disambiguated ID Type / Status
Subject Laura Herbert E87679 entity
Predicate memberOf P10 FINISHED
Object Herbert family E126083 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: Herbert family | Statement: [Laura Herbert, memberOf, Herbert family]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Herbert family
Context triple: [Laura Herbert, memberOf, Herbert family]
  • A. Herbert family chosen
    The Herbert family is a prominent British aristocratic lineage historically associated with the Earls of Powis and other notable noble titles.
  • B. Hall family
    The Hall family is a familial group or lineage to which Sylvia Hall belongs.
  • C. Talbot family
    The Talbot family is a historically prominent lineage whose influence and legacy in colonial-era Maryland led to places such as Talbot County being named in their honor.
  • D. Henry family
    The Henry family is a lineage whose surname is associated with the historic Henry House and its heritage.
  • E. Bruce family
    The Bruce family was a powerful medieval Scottish noble dynasty that produced several prominent figures, including Robert the Bruce, King of Scots.
  • 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_69aed94425148190be337845d56fac22 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefcab0a1c8190a1b0ca48ebc95b31 completed March 9, 2026, 5 p.m.
NED1 Entity disambiguation (via context triple) batch_69b56b6651d48190915581eca783cf3b completed March 14, 2026, 2:06 p.m.
Created at: March 9, 2026, 3:39 p.m.