Triple
T974623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael |
E21023
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Mickael |
E114788
|
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: Mickael | Statement: [Michael, hasVariant, Mickael]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mickael Context triple: [Michael, hasVariant, Mickael]
-
A.
Michaël
chosen
Michaël is a given name, typically a French or Dutch variant of the name Michael, used for males in various European countries.
-
B.
Micheal
Micheal is a given name, typically a variant spelling of the more common name Michael.
-
C.
Micah
Micah is a minor biblical figure in the Book of Judges known for establishing a private shrine and hiring a Levite as his personal priest, illustrating the religious disorder of the period.
-
D.
Myles
Myles is a masculine given name of English origin, historically associated with figures such as Mayflower military leader Myles Standish.
-
E.
Mikael
Mikael is a masculine given name commonly used in Scandinavian and Finnish cultures, equivalent to Michael.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b460a5c0819087b03dfb8a3af2c2 |
completed | March 1, 2026, 9:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac2586fd7c8190ba77b327bad4bb69 |
completed | March 7, 2026, 1:17 p.m. |
Created at: March 1, 2026, 7:40 p.m.