Triple
T258389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jennifer Katharine Gates |
E5486
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Jennifer |
E47548
|
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: Jennifer | Statement: [Jennifer Katharine Gates, givenName, Jennifer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jennifer Context triple: [Jennifer Katharine Gates, givenName, Jennifer]
-
A.
Jennifer
chosen
Jennifer is a common feminine given name of English origin, derived from the Cornish form of Guinevere and widely used in many English-speaking countries.
-
B.
Jane
Jane is a feminine given name of English origin that has been widely used in many English-speaking countries for centuries.
-
C.
Kathleen
Kathleen is a feminine given name of Irish origin, derived from the name Catherine and widely used in English-speaking countries.
-
D.
Kimberly
Kimberly is a feminine given name of English origin that has been widely used in the United States since the mid-20th century.
-
E.
Karen
Karen is a common feminine given name used in many English-speaking and European countries.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d703e688190bb86c69527e306f5 |
completed | Feb. 28, 2026, 3:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a405ef40248190b81d461f3b6d4baa |
completed | March 1, 2026, 9:25 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.