Triple
T847021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendrik Lorentz |
E18298
|
entity |
| Predicate | influenced |
P9
|
FINISHED |
| Object | Albert Einstein |
E318
|
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: Albert Einstein | Statement: [Hendrik Lorentz, influenced, Albert Einstein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Albert Einstein Context triple: [Hendrik Lorentz, influenced, Albert Einstein]
-
A.
Albert Einstein
chosen
Albert Einstein was a theoretical physicist best known for developing the theory of relativity and fundamentally reshaping modern physics.
-
B.
EINSTEIN
EINSTEIN is a U.S. federal intrusion detection and prevention system used to monitor and protect government agency networks from cyber threats.
-
C.
Bernhard Caesar Einstein
Bernhard Caesar Einstein was a Swiss-American engineer and the only grandchild of Albert Einstein to become a physicist.
-
D.
Rudolf Einstein
Rudolf Einstein was the father of Elsa Einstein, who was both the second wife and cousin of physicist Albert Einstein.
-
E.
Hermann Einstein
Hermann Einstein was a German engineer and businessman best known as the father of physicist Albert Einstein.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac0ba6b4819089c15ed7e1765502 |
completed | March 1, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7928f8a808190aaf5f2a2f3ee676f |
completed | March 4, 2026, 2:01 a.m. |
Created at: March 1, 2026, 7:38 p.m.