Triple
T6233974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LeBron James |
E139424
|
entity |
| Predicate | nickName |
P2937
|
FINISHED |
| Object | King James |
E139424
|
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: King James | Statement: [LeBron James, nickName, King James]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: King James Context triple: [LeBron James, nickName, King James]
-
A.
King James
chosen
King James is the widely used nickname for LeBron James, one of the greatest and most influential basketball players in NBA history.
-
B.
Stephen, King of England
Stephen, King of England, was a 12th-century monarch whose contested claim to the throne led to a prolonged civil war known as The Anarchy.
-
C.
Edward
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.
-
D.
Richard
Richard is a common masculine given name of Germanic origin, widely used in English-speaking countries.
-
E.
Rex Anglorum
Rex Anglorum is a Latin royal title historically used to denote the "King of the English" in medieval England.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062efa25c8190a54f5a6f5b5ad24f |
completed | March 22, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c20df60e488190933b7fa068e96cc4 |
completed | March 24, 2026, 4:07 a.m. |
Created at: March 22, 2026, 4:22 p.m.