Triple
T14618096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaël |
E343139
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Yael (without diaeresis) |
E343139
|
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: Yael (without diaeresis) | Statement: [Yaël, hasSpellingVariant, Yael (without diaeresis)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yael (without diaeresis) Context triple: [Yaël, hasSpellingVariant, Yael (without diaeresis)]
-
A.
Ayelet
Ayelet is a feminine given name of Hebrew origin, commonly used in Israel.
-
B.
Yaël
chosen
Yaël is a French feminine given name of Hebrew origin, commonly borne by contemporary public figures such as politicians and artists.
-
C.
Eynat
Eynat is a feminine given name of Hebrew origin, commonly used in Israel.
-
D.
Talya
Talya is a feminine given name used in various cultures, often considered a variant of names like Talia and associated with meanings such as “dew from God” or “morning dew.”
-
E.
Merav
Merav is a Hebrew feminine given name commonly used in Israel.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46550e48190af45f426f02579bb |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda924c7308190931c03fbac57b0bf |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 10, 2026, 1:25 a.m.