Triple
T15234460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann Struve |
E364087
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hermann |
E650411
|
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: Hermann | Statement: [Hermann Struve, givenName, Hermann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hermann Context triple: [Hermann Struve, givenName, Hermann]
-
A.
Hermann
Hermann is the obsessive, tormented protagonist of Alexander Pushkin’s novella "The Queen of Spades," whose fixation on a secret winning card formula leads to his psychological and moral downfall.
-
B.
Hermann
Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
-
C.
Hermann
Hermann is a German surname borne by various notable individuals across fields such as philosophy, science, and the arts.
-
D.
Hermann
chosen
Hermann is a masculine given name of Germanic origin, commonly used in German-speaking countries and historically borne by various notable figures.
-
E.
Hermann
Hermann is a fictional character appearing in the work "City of Death."
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007d7237081908dc17900ee66b64f |
completed | April 15, 2026, 9:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff133950288190a5ffeb52ee0bac37 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:12 a.m.