Triple
T20257014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Barksdale |
E498728
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Barksdale |
—
|
NE NERFINISHED |
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: Barksdale | Statement: [William Barksdale, familyName, Barksdale]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barksdale Context triple: [William Barksdale, familyName, Barksdale]
-
A.
Barksdale
chosen
Barksdale is a surname most notably associated with American executive Jim Barksdale, former CEO of Netscape Communications.
-
B.
Dobbins
Dobbins is a small unincorporated rural community located in Yuba County, California.
-
C.
Barksdale Air Force Base
Barksdale Air Force Base is a major United States Air Force installation in Louisiana known for hosting strategic bomber operations and serving as the home of Air Force Global Strike Command.
-
D.
Boyington
Boyington is a surname most notably associated with American architect William W. Boyington, known for designing prominent 19th-century buildings in Chicago.
-
E.
Hurlburt
Hurlburt is a surname of English origin borne by various notable individuals across fields such as politics, the military, and academia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674c6693081908ff8bec12f212f7b |
completed | April 20, 2026, 6:47 p.m. |
Created at: April 11, 2026, 11:41 p.m.