Triple
T23484653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seymour Hersh |
E570501
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Seymour |
—
|
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: Seymour | Statement: [Seymour Hersh, givenName, Seymour]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seymour Context triple: [Seymour Hersh, givenName, Seymour]
-
A.
Seymour
Seymour is a small unincorporated community and suburban area in eastern Tennessee, situated near Knoxville in the foothills of the Great Smoky Mountains.
-
B.
Seymour
chosen
Seymour is a masculine given name of English origin that has been borne by various notable figures in fields such as business, politics, and the arts.
-
C.
Seymour
Seymour is a small town in New Haven County, Connecticut, known for its historic industrial roots along the Naugatuck River.
-
D.
Seymour
Seymour is a regional town in central Victoria, Australia, known as a key agricultural and transport hub on the route between Melbourne and Sydney.
-
E.
Seymour
Seymour is an English surname historically associated with a prominent noble family in Tudor England.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a752c678819087e5c50b8cf87d3d |
completed | April 29, 2026, 6:38 a.m. |
Created at: April 17, 2026, 6:03 p.m.