Triple
T33229144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathy Prinze |
E850643
|
entity |
| Predicate | hasSurnameFromSpouse |
P14292
|
FINISHED |
| Object | Freddie Prinze |
—
|
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: Freddie Prinze | Statement: [Kathy Prinze, hasSurnameFromSpouse, Freddie Prinze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameFromSpouse Context triple: [Kathy Prinze, hasSurnameFromSpouse, Freddie Prinze]
-
A.
hasMarriedSurname
chosen
Indicates that a person’s current surname is the one they adopted through marriage.
-
B.
spouseFamilyName
Indicates that the object is the family name (surname) shared by or associated with a person's spouse.
-
C.
hasSurnameFromParent
Indicates that an individual’s surname is inherited from one of their parents.
-
D.
eraNameOfSpouse
Indicates that the value is the name of the historical era associated with the spouse of the subject.
-
E.
spouseMiddleName
Indicates that the specified middle name belongs to the person’s spouse.
- F. None of above.
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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 1, 2026, 1:30 a.m.