Triple
T14816210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosa Jellinek |
E348321
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Jellinek |
E320409
|
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: Jellinek | Statement: [Rosa Jellinek, familyName, Jellinek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jellinek Context triple: [Rosa Jellinek, familyName, Jellinek]
-
A.
Jellinek
chosen
Jellinek is a surname most notably associated with Mercedes Jellinek, the namesake and inspiration for the Mercedes automobile brand.
-
B.
Blanka Jellinek
Blanka Jellinek was a member of the Jellinek family, historically associated with the early development and naming of the Mercedes automobile brand.
-
C.
Helene Jellinek
Helene Jellinek was a member of the Jellinek family associated with the early history of the Mercedes automobile brand.
-
D.
Johanna Jellinek
Johanna Jellinek was a member of the Jellinek family, historically associated with the origins of the Mercedes automobile brand.
-
E.
Mira Jellinek
Mira Jellinek was a member of the Jellinek family associated with the early history of the Mercedes automobile brand, known primarily as the sister of Mercedes Jellinek.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe2c1ec81908b3dff7a5d0e85d0 |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe3897691c819085ef89480e730723 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:49 a.m.