Triple
T14525916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aharon |
E340775
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Ahron |
E340775
|
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: Ahron | Statement: [Aharon, hasVariant, Ahron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ahron Context triple: [Aharon, hasVariant, Ahron]
-
A.
Aharon
chosen
Aharon is a masculine given name of Hebrew origin, traditionally associated with the biblical figure Aaron and widely used in Jewish communities.
-
B.
Arieh
Arieh is a Hebrew given name meaning "lion," commonly used in Israel and among Jewish communities.
-
C.
Yair
Yair is a masculine given name of Hebrew origin, commonly used in Israel and among Jewish communities worldwide.
-
D.
Hanoch
Hanoch is a biblical figure listed in the Hebrew Bible as one of the descendants of Abraham through Keturah and Midian.
-
E.
Akiva
Akiva is a masculine given name of Hebrew origin, meaning "protect" or "shelter," and is notably borne by figures such as the ancient Jewish sage Rabbi Akiva and screenwriter-producer Akiva Goldsman.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea050781881909ed685d94479bf99 |
completed | April 14, 2026, 8:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd8ab07e08819085a6a21cc9cea1fa |
completed | May 8, 2026, 7:03 a.m. |
Created at: April 10, 2026, 1:22 a.m.