Triple
T22758634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John S. Mosby |
E562920
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mosby |
—
|
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: Mosby | Statement: [John S. Mosby, familyName, Mosby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mosby Context triple: [John S. Mosby, familyName, Mosby]
-
A.
Mosby
chosen
Mosby is a surname most famously associated with John S. Mosby, a Confederate cavalry battalion commander and guerrilla leader during the American Civil War.
-
B.
Buckmaster
Buckmaster is a surname most notably associated with English orchestral arranger and composer Paul Buckmaster, known for his influential work in rock and pop music.
-
C.
Mosbey
Mosbey is a variant spelling of the surname Mosby, which is associated with various individuals and places, particularly in the United States.
-
D.
McDowell
McDowell is a surname of Scottish origin borne by various notable individuals, including American Civil War general Irvin McDowell.
-
E.
Mustin
Mustin is a surname most notably associated with a U.S. Navy family whose members were pioneers in naval aviation and distinguished military service.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a7a8ca481909953dcd6fbcc5fcf |
completed | April 29, 2026, 3:26 a.m. |
Created at: April 17, 2026, 3:25 p.m.