Triple
T4597551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz |
E100240
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Lorenz |
E275141
|
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: Lorenz | Statement: [Lorentz, hasVariant, Lorenz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lorenz Context triple: [Lorentz, hasVariant, Lorenz]
-
A.
Lorenz
chosen
Lorenz is a masculine given name of German origin, historically borne by various notable figures in Europe.
-
B.
Rabinovich
Rabinovich is a Jewish surname of Eastern European origin, notably borne by the Yiddish writer Sholem Aleichem (born Sholem Rabinovich).
-
C.
Lindemann
Lindemann is a German surname most notably associated with Ferdinand von Lindemann, the mathematician who proved that π is a transcendental number.
-
D.
Lorens
Lorens is a character from Paulo Coelho’s novel "Brida," serving as one of the key figures in the protagonist’s spiritual and personal journey.
-
E.
Saffman
Saffman is a surname most notably associated with Philip G. Saffman, a prominent British-American applied mathematician and fluid dynamicist.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59420c108190b5c2c5039e964da5 |
completed | March 20, 2026, 2:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdfa4f26d08190b9978c579623adcb |
completed | March 21, 2026, 1:54 a.m. |
Created at: March 20, 2026, 1:11 p.m.