Triple
T30550397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother Tucker |
E777540
|
entity |
| Predicate | hasParentSeriesCreator |
P173279
|
FINISHED |
| Object | Seth MacFarlane |
—
|
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: Seth MacFarlane | Statement: [Mother Tucker, hasParentSeriesCreator, Seth MacFarlane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentSeriesCreator Context triple: [Mother Tucker, hasParentSeriesCreator, Seth MacFarlane]
-
A.
hasHostSeriesCreator
Indicates that an entity serves as the creator of the host series associated with another entity.
-
B.
hasParentSeries
Indicates that a work or item belongs to, or is derived from, a broader parent series.
-
C.
hasCreatorFamilyRelation
Indicates that an entity’s creator is related by family (e.g., parent, sibling, spouse, or other kinship) to another specified person.
-
D.
isFromSeriesCreatedBy
chosen
Indicates that one entity originates from, or is part of, a series that was created by another entity.
-
E.
hasCreatorRelationshipToSubject
Indicates that an entity stands in a creator role with respect to the subject, meaning it is responsible for bringing the subject into existence or producing it.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 29, 2026, 8:20 p.m.