Triple
T22753780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jane Wolfe |
E562779
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Sarah |
—
|
NE NERFINISHED |
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: Sarah | Statement: [Jane Wolfe, givenName, Sarah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sarah Context triple: [Jane Wolfe, givenName, Sarah]
-
A.
Sarah
Sarah is the given name of Sarah P. Duke, the philanthropist and namesake of Duke University's Sarah P. Duke Gardens.
-
B.
Sarah
Sarah is the given name of the renowned 19th- and early 20th-century French stage actress Sarah Bernhardt, often called "the Divine Sarah."
-
C.
Sarah
Sarah is the given name of Sarah Thompson, Countess Rumford, an 18th–19th century noblewoman known for her association with the scientist and inventor Benjamin Thompson (Count Rumford).
-
D.
Sarah
Sarah is a person closely associated with Jimmy as a trusted friend or partner in a shared cause or context.
-
E.
Sarah
Sarah is a noblewoman of the Boyle family, historically styled Lady Sarah Boyle.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
Provenance (2 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bb80ac8190b53a1e00704c4ff5 |
completed | April 29, 2026, 3:23 a.m. |
Created at: April 17, 2026, 3:25 p.m.