Triple
T6241981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John H. Bankhead |
E139624
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | John |
E55602
|
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: [John H. Bankhead, givenName, John]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: John Context triple: [John H. Bankhead, givenName, John]
-
A.
John
chosen
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
John is the given name of John Arbuthnot Fisher, a prominent British admiral and naval reformer of the late 19th and early 20th centuries.
-
C.
John
John is the given name of the American composer John Luther Adams, known for his works inspired by nature and environmental themes.
-
D.
John
John is the first name of John Dashwood, a character in Jane Austen's novel "Sense and Sensibility."
-
E.
John
John is the first name of the fictional character John Connor, the prophesied leader of the human resistance in the Terminator franchise.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0630797f88190a5571f6000ba2e3b |
completed | March 22, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5190757648190a73575e680a35684 |
completed | March 26, 2026, 11:31 a.m. |
Created at: March 22, 2026, 4:23 p.m.