Triple
T14358282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Leavy |
E356028
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
Leavy
Leavy is a surname most notably associated with Bill Leavy, an American football official in the National Football League.
|
E1094742
|
NE FINISHED |
How this triple was built (4 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: Leavy | Statement: [Bill Leavy, familyName, Leavy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leavy Context triple: [Bill Leavy, familyName, Leavy]
-
A.
Leahey
Leahey is a surname variant of Leahy, an Irish family name of Gaelic origin.
-
B.
Lavery
Lavery is a surname of Irish origin borne by various notable individuals, including figures in the arts, politics, and sports.
-
C.
Levy
Levy is a variant spelling of the name Levi, commonly used as a Jewish surname and sometimes as a given name.
-
D.
Rainey
Rainey is a surname most notably associated with Henry T. Rainey, a prominent American politician who served as Speaker of the U.S. House of Representatives in the early 1930s.
-
E.
Lapham
Lapham is a surname most notably associated with Roger D. Lapham, an American shipping executive and former mayor of San Francisco.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Leavy Triple: [Bill Leavy, familyName, Leavy]
Generated description
Leavy is a surname most notably associated with Bill Leavy, an American football official in the National Football League.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Leavy Target entity description: Leavy is a surname most notably associated with Bill Leavy, an American football official in the National Football League.
-
A.
Leahey
Leahey is a surname variant of Leahy, an Irish family name of Gaelic origin.
-
B.
Lavery
Lavery is a surname of Irish origin borne by various notable individuals, including figures in the arts, politics, and sports.
-
C.
Levy
Levy is a variant spelling of the name Levi, commonly used as a Jewish surname and sometimes as a given name.
-
D.
Rainey
Rainey is a surname most notably associated with Henry T. Rainey, a prominent American politician who served as Speaker of the U.S. House of Representatives in the early 1930s.
-
E.
Lapham
Lapham is a surname most notably associated with Roger D. Lapham, an American shipping executive and former mayor of San Francisco.
- F. None of above. chosen
Provenance (5 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f52ca7881908704eef20228aed3 |
completed | April 14, 2026, 7:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c48dd408190ac45ad4ca6f610c3 |
completed | May 8, 2026, 2:36 a.m. |
| NEDg | Description generation | batch_69fd4cf6e6788190a98479ed3b615a4e |
completed | May 8, 2026, 2:39 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fd4d6dd7c481908f53f8902ee714dd |
completed | May 8, 2026, 2:41 a.m. |
Created at: April 10, 2026, 1:15 a.m.