Triple
T16459325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horace Trumbauer |
E399764
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Trumbauer |
E399764
|
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: Trumbauer | Statement: [Horace Trumbauer, familyName, Trumbauer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Trumbauer Context triple: [Horace Trumbauer, familyName, Trumbauer]
-
A.
Trumbauer
chosen
Trumbauer is a surname most notably associated with American architect Horace Trumbauer, known for his grand Gilded Age mansions and institutional buildings.
-
B.
Seiberling
Seiberling is a surname most notably associated with American industrialist Frank Seiberling, co-founder of the Goodyear Tire & Rubber Company.
-
C.
Gallaher
Gallaher is a surname of Irish origin borne by various notable individuals, including figures in sports, politics, and the arts.
-
D.
Altmeyer
Altmeyer is a surname most notably associated with Arthur J. Altmeyer, a key architect of the U.S. Social Security system.
-
E.
Stöcker
Stöcker is a German surname that is a variant of the name Stoker.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d7ff0e881909100bb5b33c04291 |
completed | April 18, 2026, 7:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f53aff081909a75de6672f15f0e |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:10 a.m.