Triple
T19603743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zach Britton |
E470548
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Britton |
—
|
NE NERFINISHED |
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: Britton | Statement: [Zach Britton, familyName, Britton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Britton Context triple: [Zach Britton, familyName, Britton]
-
A.
Britton
chosen
Britton is an English surname borne by various notable individuals across fields such as politics, sports, and the arts.
-
B.
Orleton
Orleton is a small rural village in Herefordshire, England, known for its historic church and traditional countryside setting near the English–Welsh border.
-
C.
Breighton
Breighton is a small rural village in the East Riding of Yorkshire, England, situated within the historic area of Howdenshire.
-
D.
Bettany
Bettany is an English surname most notably associated with actor Paul Bettany.
-
E.
Brettingham
Brettingham is an English surname historically associated with a family of notable 18th-century architects, including Matthew Brettingham the Younger.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64081af6c8190868b73b07c874cd5 |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.