Triple
T1860456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myer |
E34798
|
entity |
| Predicate | variantOf |
P4680
|
FINISHED |
| Object | Mayer |
E143547
|
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: Mayer | Statement: [Myer, variantOf, Mayer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mayer Context triple: [Myer, variantOf, Mayer]
-
A.
Mayer
chosen
Mayer is a common German-origin surname borne by numerous notable individuals across fields such as music, science, and politics.
-
B.
Meyer
Meyer is a given name most famously associated with Meyer Lansky, a major organized crime figure in the United States during the 20th century.
-
C.
Maynard
Maynard is the middle name of the influential British economist John Maynard Keynes, a key figure in modern macroeconomic theory.
-
D.
Menzel
Menzel is the surname of Idina Menzel, the American actress and singer best known for her roles in Broadway musicals and the film "Frozen."
-
E.
Morgenstern
Morgenstern is a German surname borne by various notable figures in fields such as economics, literature, 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb09caee881908efe8aa38471298c |
completed | March 7, 2026, 4:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69add1ce296c819093336cbaa257dfd2 |
completed | March 8, 2026, 7:45 p.m. |
Created at: March 4, 2026, 7:34 p.m.