Triple
T3054758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Stevens |
E60453
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Stevens |
E26256
|
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: Stevens | Statement: [Ted Stevens, familyName, Stevens]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stevens Context triple: [Ted Stevens, familyName, Stevens]
-
A.
Stevens
chosen
Stevens is a common English-language surname borne by numerous notable individuals across fields such as sports, politics, arts, and academia.
-
B.
Hillegas
Hillegas is a surname most notably associated with Michael Hillegas, the first Treasurer of the United States.
-
C.
Rutledge
Rutledge is a small town in eastern Tennessee that serves as the county seat of Grainger County within the Knoxville metropolitan area.
-
D.
Rutledge
Rutledge is a surname of English and Scottish origin borne by various notable individuals in politics, law, and other fields.
-
E.
Shaughnessy
Shaughnessy is an affluent residential neighbourhood in Vancouver, British Columbia, known for its large heritage homes and tree-lined streets.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf6b9948190bc957bfd1579c471 |
completed | March 8, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1ef03425c8190a44486ab563c210f |
completed | March 11, 2026, 10:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.