Triple
T27936675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katzin |
E700631
|
entity |
| Predicate | isFamilySurnameOf |
P110914
|
FINISHED |
| Object | Stubby Kaye |
—
|
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: Stubby Kaye | Statement: [Katzin, isFamilySurnameOf, Stubby Kaye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFamilySurnameOf Context triple: [Katzin, isFamilySurnameOf, Stubby Kaye]
-
A.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
B.
isSurname
chosen
Indicates that one entity is the family name (last name) of another entity.
-
C.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
D.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
E.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:13 p.m.