Triple
T3869076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zac |
E91934
|
entity |
| Predicate | alternativeSpelling |
P457
|
FINISHED |
| Object | Zak |
E91934
|
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: Zak | Statement: [Zac, alternativeSpelling, Zak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zak Context triple: [Zac, alternativeSpelling, Zak]
-
A.
Zac
chosen
Zac is a common shortened form of the given name Isaac.
-
B.
Zay
Zay is the surname of Jean Zay, a notable French politician and Minister of National Education and Fine Arts during the 1930s.
-
C.
Zeke
Zeke is a central male character in the romantic comedy film "Think Like a Man," known for navigating modern dating dynamics alongside a group of friends influenced by a relationship advice book.
-
D.
Zeke
Zeke is the Allied reporting name for the Mitsubishi A6M Zero, the famous Japanese carrier-based fighter aircraft used extensively during World War II.
-
E.
Zan
Zan is a collective term for a group of closely related Kartvelian languages spoken primarily in western Georgia, including Mingrelian and Laz.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3dfb3c8190a0a07070f0d76bf6 |
completed | March 9, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b512440b8c8190ae2048bfcdd565ec |
completed | March 14, 2026, 7:46 a.m. |
Created at: March 9, 2026, 3:20 p.m.