Triple
T8862563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josiah Parsons Cooke |
E210927
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Cooke |
E65201
|
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: Cooke | Statement: [Josiah Parsons Cooke, familyName, Cooke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cooke Context triple: [Josiah Parsons Cooke, familyName, Cooke]
-
A.
Cooke
chosen
Cooke is a surname of English origin, often considered a variant spelling of "Cook."
-
B.
Cooke Enterprises
Cooke Enterprises was a private business conglomerate owned and operated by sports and media magnate Jack Kent Cooke, encompassing his diverse investments and ventures.
-
C.
Optica
Optica is a leading scientific society dedicated to advancing the study and application of optics and photonics worldwide.
-
D.
Bell & Howell
Bell & Howell is an American company historically known for producing motion picture cameras, projectors, and other audiovisual and imaging equipment.
-
E.
Barco
Barco is a surname most notably associated with Argentine professional footballer Ezequiel Barco.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc610263048190931bb2c3ac573a08 |
completed | April 1, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfa0c248108190815d593f44029183 |
completed | April 3, 2026, 11:13 a.m. |
Created at: March 30, 2026, 6:50 p.m.