Triple
T18532231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tess Gerritsen |
E452859
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Gerritsen |
—
|
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: Gerritsen | Statement: [Tess Gerritsen, hasFamilyName, Gerritsen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gerritsen Context triple: [Tess Gerritsen, hasFamilyName, Gerritsen]
-
A.
Gerritsen
chosen
Gerritsen is a Dutch-origin surname borne by various notable individuals, including authors, athletes, and public figures.
-
B.
Berghuizen
Berghuizen is a small village located within the municipality of De Wolden in the Dutch province of Drenthe.
-
C.
Meyer-Hetling
Meyer-Hetling is a German surname most notably associated with Konrad Meyer-Hetling, an agronomist and SS officer involved in Nazi settlement planning.
-
D.
Gerrity
Gerrity is a surname, likely of Irish origin, that serves as a spelling variant of the name Gerry.
-
E.
Jacob Gerritsen
Jacob Gerritsen is known primarily as the husband of bestselling medical thriller author Tess Gerritsen.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533fe35288190977c85ee0bb96264 |
completed | April 19, 2026, 7:58 p.m. |
Created at: April 10, 2026, 11:37 a.m.