Triple
T25535076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Kids Edition |
E640019
|
entity |
| Predicate | hasParentalControlType |
P168890
|
FINISHED |
| Object | time limits |
—
|
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: time limits | Statement: [Fire Kids Edition, hasParentalControlType, time limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentalControlType Context triple: [Fire Kids Edition, hasParentalControlType, time limits]
-
A.
hasParentalUnit
Indicates that an entity has a parent or guardian that serves as its primary caregiving or parental figure.
-
B.
familyControlled
Indicates that an entity is owned or effectively governed by one or more members of the same family, who hold decisive control over its decisions or operations.
-
C.
parentStudio
Indicates that one studio serves as the parent or owning studio of another studio.
-
D.
hasParentSystem
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
-
E.
hasGuardianReview
Indicates that something has been reviewed or critiqued in a piece published by The Guardian.
- F. None of above. chosen
Provenance (4 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 21, 2026, 3:22 p.m.