Triple
T12529358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enrique |
E299519
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Heinrich |
E70531
|
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: Heinrich | Statement: [Enrique, hasVariant, Heinrich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heinrich Context triple: [Enrique, hasVariant, Heinrich]
-
A.
Heinrich
chosen
Heinrich is a masculine given name of German origin that has been borne by numerous historical figures, including nobility, scholars, and political leaders.
-
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 masculine given name of Germanic origin, commonly used in German-speaking countries and historically borne by various notable figures.
-
D.
Hermann
Hermann is a fictional character appearing in the work "City of Death."
-
E.
Hermann
Hermann is a German surname borne by various notable individuals across fields such as philosophy, science, and the arts.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9545e90948190980bd4d64964a0f2 |
completed | April 10, 2026, 7:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6718cd6288190ad080f469f334caf |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 8, 2026, 9:57 p.m.