Triple
T35081159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FoxBox |
E1012439
|
entity |
| Predicate | programmingSupplier |
P51827
|
FINISHED |
| Object | 4Kids Entertainment |
—
|
NE NERFINISHED |
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: 4Kids Entertainment | Statement: [FoxBox, programmingSupplier, 4Kids Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingSupplier Context triple: [FoxBox, programmingSupplier, 4Kids Entertainment]
-
A.
developerOfWork
Indicates that one entity is the creator or producer responsible for making or developing a particular work.
-
B.
providerOf
chosen
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
C.
providedProgramming
Indicates that one entity supplied or made available programming (such as software, code, or a program) to another entity.
-
D.
developerOccupation
Indicates that an entity works in a developer role or profession, such as software or application development.
-
E.
softwareEngine
Indicates that an entity functions as a software engine, i.e., a core computational or processing component that drives or powers software operations for another entity.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.