Triple
T8874372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Cochran |
E211234
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Cochran |
E228771
|
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: Cochran | Statement: [Steve Cochran, hasFamilyName, Cochran]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cochran Context triple: [Steve Cochran, hasFamilyName, Cochran]
-
A.
Cochran
chosen
Cochran is a surname of Scottish origin borne by various notable individuals in fields such as politics, science, and the arts.
-
B.
Cochran
Cochran is a small city in central Georgia that serves as the economic and cultural hub of rural Bleckley County.
-
C.
Hartigan
Hartigan is a surname most notably associated with Grace Hartigan, a prominent American Abstract Expressionist painter.
-
D.
Cochran Square
Cochran Square is a public square located in the coastal city of Brunswick, Georgia.
-
E.
Tukey
Tukey is the surname of John W. Tukey, a prominent American statistician known for pioneering exploratory data analysis and coining the term "bit."
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc614451d081908804430a72d00edf |
completed | April 1, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfa0f9714c8190909587eecbb10e1a |
completed | April 3, 2026, 11:14 a.m. |
Created at: March 30, 2026, 6:52 p.m.