Triple
T10630669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamara |
E250443
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Tamar |
E108446
|
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: Tamar | Statement: [Tamara, hasVariant, Tamar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tamar Context triple: [Tamara, hasVariant, Tamar]
-
A.
Tamar
chosen
Tamar is a biblical figure in the Book of 2 Samuel, known as the daughter of King David whose tragic story of abuse and injustice profoundly impacts David’s family narrative.
-
B.
Tamar
"Tamar" is the self-titled debut studio album by American R&B singer Tamar Braxton, showcasing her early solo artistry and vocal style.
-
C.
Tirza
Tirza is a river in Latvia that serves as one of the tributaries feeding into the larger Gauja River system.
-
D.
Jerusha
Jerusha is a feminine given name of Hebrew origin, traditionally interpreted to mean "possession" or "inheritance."
-
E.
Tamara
Tamara is a feminine given name of Hebrew origin, commonly used in various cultures and languages.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df93a2b88190a0f3a52b8e88f54f |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d96bb4bbf08190994ea9123c0b2dab |
completed | April 10, 2026, 9:29 p.m. |
Created at: April 8, 2026, 9:01 p.m.