Triple
T13394385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Tannen |
E319661
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Tannen |
E763777
|
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: Tannen | Statement: [Charles Tannen, familyName, Tannen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tannen Context triple: [Charles Tannen, familyName, Tannen]
-
A.
Tannen
chosen
Tannen is the surname of the antagonistic outlaw family featured in the Back to the Future film series, most notably characters like Biff and Buford "Mad Dog" Tannen.
-
B.
Tannenbaum
Tannenbaum is a surname of German origin borne by various individuals, including the mobster Allie "Tick Tock" Tannenbaum.
-
C.
Birch
Birch is a masculine given name most notably borne by American politician Birch Bayh, a long-serving U.S. senator from Indiana.
-
D.
Ahorn
Ahorn is a municipality in the Bavarian region of Germany, known for its rural character and proximity to the city of Coburg.
-
E.
Tanne
Tanne is a small village in the Harz region of central Germany, now part of the town of Oberharz am Brocken.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d892d08190b1b192b93fe3d72d |
completed | April 12, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7306fb8348190a325a07a1ac858fd |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:34 p.m.