Triple
T7643786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Earl Jones |
E173071
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Jones |
E46350
|
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: Jones | Statement: [James Earl Jones, familyName, Jones]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jones Context triple: [James Earl Jones, familyName, Jones]
-
A.
Jones
chosen
Jones is a common English-language surname borne by numerous notable individuals across fields such as entertainment, sports, politics, and science.
-
B.
John
John is the given first name of the legendary American professional golfer Byron Nelson, one of the sport’s early great champions.
-
C.
John
John is the given name of Sir John Colborne, a British Army officer and colonial administrator who served as Lieutenant Governor of Upper Canada and later as Lord Seaton.
-
D.
John
John is the given name of the American historian and author John W. Dower, known for his influential works on modern Japanese history and World War II.
-
E.
John
John is the given name of Sir John Byron, an English nobleman and Royalist commander during the English Civil War.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faf13858819095262664e1e04eb7 |
completed | March 27, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c870d510f08190ad7706f582e8c1a0 |
completed | March 29, 2026, 12:22 a.m. |
Created at: March 27, 2026, 3:58 p.m.