Triple
T20864106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gumm family |
E513703
|
entity |
| Predicate | hasFamilyProfession |
P96643
|
FINISHED |
| Object | performing arts |
—
|
LITERAL 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: performing arts | Statement: [The Gumm family, hasFamilyProfession, performing arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyProfession Context triple: [The Gumm family, hasFamilyProfession, performing arts]
-
A.
familyProfession
chosen
Indicates that a person’s profession is shared with or traditionally practiced within their family, reflecting an occupational lineage or family trade.
-
B.
parentOccupation
Indicates that one entity has an occupation which is the job or profession of the other entity’s parent.
-
C.
hasGivenProfession
Indicates that an entity holds or practices a specified profession or occupation.
-
D.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
E.
hasFamilyRelationInWork
Indicates that there exists a family relationship between two entities within the context of a specific work (e.g., book, film, or other creative work).
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c45e51f08190ac1ff59280ad741b |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.