Triple
T13987405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semi-Homemade Cooking |
E336475
|
entity |
| Predicate | relatedShowType |
P73830
|
FINISHED |
| Object | food reality television |
—
|
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: food reality television | Statement: [Semi-Homemade Cooking, relatedShowType, food reality television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedShowType Context triple: [Semi-Homemade Cooking, relatedShowType, food reality television]
-
A.
associatedShowType
chosen
Indicates a relationship where one entity is linked to the type or category of show with which it is associated.
-
B.
associatedShow
Indicates a relationship where one entity is linked or connected to a particular show (e.g., as its subject, source, or related program).
-
C.
relatedShowElement
Indicates that one show element is associated with or connected to another show element in some relevant way.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea537408190bb9d35963886803f |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.