Triple
T12911206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kids' WB |
E308867
|
entity |
| Predicate | onlineSuccessor |
P102666
|
FINISHED |
| Object | KidsWB.com streaming site |
—
|
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: KidsWB.com streaming site | Statement: [Kids' WB, onlineSuccessor, KidsWB.com streaming site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlineSuccessor Context triple: [Kids' WB, onlineSuccessor, KidsWB.com streaming site]
-
A.
namedSuccessor
Indicates that one entity has been explicitly designated as the successor or heir to another entity.
-
B.
ethnicSuccessor
Indicates that one ethnic group is the successor or continuation of another, typically inheriting its identity, culture, or population in a historical or social sense.
-
C.
platformSuccessor
chosen
Indicates that one platform directly follows or replaces another in a sequence or evolution of platforms.
-
D.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
E.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9719f96248190b746f9d4a468560c |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.