Triple
T37927545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ms. Bitters |
E946132
|
entity |
| Predicate | presentInWorkType |
P86785
|
FINISHED |
| Object | animated television series |
—
|
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: animated television series | Statement: [Ms. Bitters, presentInWorkType, animated television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentInWorkType Context triple: [Ms. Bitters, presentInWorkType, animated television series]
-
A.
basedOnWorkTypeOftenAppearsIn
Indicates that something of a given work type frequently appears in or is commonly found within another context or medium.
-
B.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
C.
grantedForWorkType
Indicates that a permission, license, or authorization is given specifically in connection with a particular type or category of work.
-
D.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
E.
appearsInWorkForm
Indicates that something is included or manifested within a particular work or version/form of a 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:20 p.m.