Triple
T13446265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilford Brimley |
E320491
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Brimley |
E320491
|
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: Brimley | Statement: [Wilford Brimley, hasSurname, Brimley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brimley Context triple: [Wilford Brimley, hasSurname, Brimley]
-
A.
Brimley
chosen
Brimley is a surname most notably associated with American actor Wilford Brimley, known for his roles in film, television, and commercials.
-
B.
Halliford
Halliford is a locality in Surrey, England, known as part of the Shepperton and Upper Halliford suburban area within the London commuter belt.
-
C.
Byington
Byington is a former name of the community now known as Karns in Tennessee.
-
D.
Bingam
Bingam is a variant form of the name Bingham, which is used as both a surname and a place name in English-speaking regions.
-
E.
Bromfield
Bromfield is a small village and civil parish in the Allerdale district of Cumbria in north-west England.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef5f610819092cad33ef72075ff |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f73998221c8190a2d8982a3da28ec9 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:40 p.m.