Triple
T10405027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kids: Non-Scripted Entertainment |
E245239
|
entity |
| Predicate | includesFormats |
P33419
|
FINISHED |
| Object | game shows |
—
|
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: game shows | Statement: [Kids: Non-Scripted Entertainment, includesFormats, game shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFormats Context triple: [Kids: Non-Scripted Entertainment, includesFormats, game shows]
-
A.
includeFormat
chosen
Indicates that one entity contains or specifies the format or representation type of another entity.
-
B.
excludesFormat
Indicates that one entity explicitly disallows or omits a particular format from the set of acceptable or supported formats in a given context.
-
C.
containerFormats
Indicates that one entity serves as a container or packaging format used to hold, encapsulate, or structure the contents of another entity.
-
D.
relatedFormat
Indicates that two resources are available in different but closely related formats or media representations of essentially the same content.
-
E.
includesWildForm
Indicates that something contains or encompasses a wild or non-domesticated form of 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9e5fb58819081d7d3e1dc625197 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:08 p.m.