Triple
T2875477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert John Riggins |
E56867
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | John |
E93597
|
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: John | Statement: [Robert John Riggins, nickname, John]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: John Context triple: [Robert John Riggins, nickname, John]
-
A.
John
John is a masculine given name of Hebrew origin, widely used in English-speaking countries and borne by numerous historical and contemporary figures.
-
B.
John
chosen
John is the nickname of John Riggins, a former American football running back best known for his Hall of Fame career with the Washington Redskins in the NFL.
-
C.
John
John is the given name of John Hancock, a prominent American statesman and patriot best known for his large signature on the United States Declaration of Independence.
-
D.
John
John is the given name of John F. Sattler, likely referring to him in a more informal or abbreviated context.
-
E.
John
John is a male individual sharing the given name "John" with his younger brother, John Pitt.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe004a64481908f1897d9054a7368 |
completed | March 7, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b01d81e76c8190aae5e6dd9b13e28b |
completed | March 10, 2026, 1:32 p.m. |
Created at: March 6, 2026, 10:03 p.m.