Triple
T639181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoover |
E16693
|
entity |
| Predicate | derivedFrom |
P909
|
FINISHED |
| Object | Huber |
E79860
|
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: Huber | Statement: [Hoover, derivedFrom, Huber]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Huber Context triple: [Hoover, derivedFrom, Huber]
-
A.
Huber
chosen
Huber is a surname of German origin that is borne by various notable individuals across fields such as science, sports, and the arts.
-
B.
Morgenstern
Morgenstern is a German surname borne by various notable figures in fields such as economics, literature, and the arts.
-
C.
Bernhard
Bernhard is a male given name of Germanic origin, historically borne by various European nobles and royals, including Prince Bernhard of the Netherlands.
-
D.
Schröder
Schröder is a common German surname borne by numerous notable figures in politics, sports, and the arts.
-
E.
Bertrando
Bertrando is an Italian given name and surname, historically borne by several notable figures including nobles and churchmen.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f00260081909d1a679182e23d10 |
completed | March 1, 2026, 8:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a5778daa0881908311823d8db543ae |
completed | March 2, 2026, 11:42 a.m. |
Created at: March 1, 2026, 7:35 p.m.