Triple
T21172517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward N. Lorenz |
E521726
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lorenz |
—
|
NE NERFINISHED |
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: [Edward N. Lorenz, familyName, Lorenz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lorenz Context triple: [Edward N. Lorenz, familyName, Lorenz]
-
A.
Lorenz
chosen
Lorenz is a masculine given name of German origin, historically borne by various notable figures in Europe.
-
B.
Eckman
Eckman is a surname most notably associated with Charley Eckman, an American basketball referee, coach, and sportscaster.
-
C.
Feigenbaum
Feigenbaum is a surname most notably associated with Edward Feigenbaum, a pioneering American computer scientist known as the "father of expert systems."
-
D.
Rabinovich
Rabinovich is a Jewish surname of Eastern European origin, notably borne by the Yiddish writer Sholem Aleichem (born Sholem Rabinovich).
-
E.
Lindtman
Lindtman is a Finnish surname most notably borne by politician Antti Lindtman.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e727141b7c81908eb8ca92850736a4 |
completed | April 21, 2026, 7:28 a.m. |
Created at: April 16, 2026, 3 p.m.