Triple
T18177375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TV Parental Guidelines |
E435197
|
entity |
| Predicate | contentDescriptor |
P130758
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [TV Parental Guidelines, contentDescriptor, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentDescriptor Context triple: [TV Parental Guidelines, contentDescriptor, D]
-
A.
contentDescriptorScope
Indicates the contextual scope or domain within which a particular content descriptor is intended to apply.
-
B.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
C.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
D.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
E.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df5a72008190bd2e56205b995a87 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.