Triple
T981575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fletcher Henderson |
E21179
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Henderson |
E29254
|
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: Henderson | Statement: [Fletcher Henderson, familyName, Henderson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henderson Context triple: [Fletcher Henderson, familyName, Henderson]
-
A.
Henderson
chosen
Henderson is a major city in the Las Vegas metropolitan area known for its rapid growth, residential communities, and proximity to the Las Vegas Strip.
-
B.
Avondale
Avondale is a well-known residential and commercial suburb of Harare, Zimbabwe, noted for its shopping centers and relatively affluent character.
-
C.
Fort Morgan
Fort Morgan is a historic 19th-century masonry fort on Mobile Bay in Alabama, best known for its role in the American Civil War, particularly the Battle of Mobile Bay.
-
D.
Erlanger
Erlanger is a surname of French origin most notably associated with historian and diplomat Philippe Erlanger.
-
E.
Shafter
Shafter is a surname most notably associated with William R. Shafter, a U.S. Army general who served in the American Civil War and the Spanish–American 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b47cbca48190a01880bb411e80bd |
completed | March 1, 2026, 9:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac66179f908190b3f0144d1ee91a1c |
completed | March 7, 2026, 5:53 p.m. |
Created at: March 1, 2026, 7:41 p.m.