Triple
T9004191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brad Cox |
E215102
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Cox |
E84235
|
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: Cox | Statement: [Brad Cox, familyName, Cox]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cox Context triple: [Brad Cox, familyName, Cox]
-
A.
Cox
chosen
Cox is a common English surname of British and Irish origin, borne by numerous notable figures across politics, law, entertainment, and sports.
-
B.
Paxson
Paxson is a small unincorporated community in Alaska known as a remote junction and stopping point for travelers in the state's interior.
-
C.
Cox Enterprises
Cox Enterprises is a major U.S. privately held media, communications, and automotive services conglomerate.
-
D.
Cowan
Cowan is a Scottish-origin surname borne by various notable individuals across fields such as politics, science, and the arts.
-
E.
Couper
Couper is a surname and variant spelling of Cooper, used by various individuals and families, particularly in English-speaking regions.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6959497c8190a748c78504dd2eb6 |
completed | April 1, 2026, 12:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfd0e3f0c88190ae688632be25e5c9 |
completed | April 3, 2026, 2:38 p.m. |
Created at: March 30, 2026, 7:05 p.m.