Triple
T4958997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartoon Network Australia |
E111356
|
entity |
| Predicate | tailorsProgrammingFor |
P61437
|
FINISHED |
| Object | Australian audience |
—
|
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: Australian audience | Statement: [Cartoon Network Australia, tailorsProgrammingFor, Australian audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailorsProgrammingFor Context triple: [Cartoon Network Australia, tailorsProgrammingFor, Australian audience]
-
A.
tailorsCreditsFor
Indicates that one party customizes or adjusts credits to suit the needs, characteristics, or context of another party.
-
B.
formerProgrammingFocus
Indicates that an entity previously concentrated on a particular programming-related area or activity, but no longer does so.
-
C.
worksOnProgram
Indicates that an entity is actively involved in contributing effort or performing tasks on a particular program.
-
D.
hasProgrammingFocus
Indicates that something is centered on, specialized in, or primarily concerned with programming.
-
E.
madeProgram
Indicates that one entity created, developed, or authored a program (such as software or a coded application).
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:32 p.m.