Triple

T7957948
Position Surface form Disambiguated ID Type / Status
Subject Bob Boone E184786 entity
Predicate father P120 FINISHED
Object Ray Boone E186015 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: Ray Boone | Statement: [Bob Boone, father, Ray Boone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ray Boone
Context triple: [Bob Boone, father, Ray Boone]
  • A. Ray Boone chosen
    Ray Boone was an American Major League Baseball infielder and two-time All-Star who played primarily in the 1940s and 1950s and is part of a three-generation MLB family.
  • B. Frank Boone
    Frank Boone is a person notable enough to be recognized as a bearer of the surname Boone, though specific widely known public details about him are not clearly established.
  • C. Brian Boone
    Brian Boone is a relatively obscure individual whose primary public mention appears to be as a namesake or example bearer of the surname Boone.
  • D. Larry Boone
    Larry Boone is an American country music singer and songwriter known for his late-1980s recording career and for writing hits for other Nashville artists.
  • E. Kenneth Boone
    Kenneth Boone is an individual notable enough to be recognized as a prominent bearer of the surname Boone.
  • 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_69ca8293a2388190aace944d7ed9c0c0 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3b7ebb24819094bc011d51ef63fb completed March 31, 2026, 3:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe072ef4c8190a8e078c5280913db completed March 31, 2026, 2:55 p.m.
Created at: March 30, 2026, 5:11 p.m.