Triple
T35067724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be Sweet |
E1011775
|
entity |
| Predicate | isTelevisionType |
P139336
|
FINISHED |
| Object | animated series episode |
—
|
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 series episode | Statement: [Be Sweet, isTelevisionType, animated series episode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTelevisionType Context triple: [Be Sweet, isTelevisionType, animated series episode]
-
A.
isTelevisionShowType
chosen
Indicates that one entity is a specific type or category of television show in relation to another entity.
-
B.
televisionServiceType
Indicates the specific kind or category of television service provided or used in the relationship.
-
C.
televisionSystemType
Indicates the type or category of television system associated with an entity (e.g., analog, digital, cable, satellite).
-
D.
televisionCategory
Indicates the classification or genre category assigned to a television-related entity (such as a show, channel, or program).
-
E.
televisionPlatform
Indicates that one entity serves as the television platform (e.g., service, system, or distribution channel) through which the other entity’s TV content is delivered or accessed.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.