Triple
T13904083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vincent Edward Jackson |
E334300
|
entity |
| Predicate | middleName |
P143
|
FINISHED |
| Object | Edward |
E5488
|
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: Edward | Statement: [Vincent Edward Jackson, middleName, Edward]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edward Context triple: [Vincent Edward Jackson, middleName, Edward]
-
A.
Edward
chosen
Edward is a masculine given name of English origin, historically associated with kings of England and notable figures such as U.S. Senator Edward M. Kennedy.
-
B.
Richard
Richard is a common masculine given name of Germanic origin, widely used in English-speaking countries.
-
C.
George
George is the given name of George W. McLaurin, the first African American student admitted to the University of Oklahoma.
-
D.
George
George is the given name of John Stewart-Murray, the 8th Duke of Atholl, a Scottish peer and soldier of the late 19th and early 20th centuries.
-
E.
George
George is the given first name of American former soccer player Eddie Pope.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25db1e308190aaed6a21e443cc44 |
completed | April 14, 2026, 11:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1c26ba08190b19560123691fda4 |
completed | May 6, 2026, 8:17 p.m. |
Created at: April 9, 2026, 10:16 p.m.