Triple
T7536555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Films and Entertainment |
E178164
|
entity |
| Predicate | categoryScope |
P17067
|
FINISHED |
| Object | screen-based media |
—
|
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: screen-based media | Statement: [Films and Entertainment, categoryScope, screen-based media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryScope Context triple: [Films and Entertainment, categoryScope, screen-based media]
-
A.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
B.
scopeOfProducts
Indicates the range or extent of products that fall under a particular category, responsibility, or context.
-
C.
collectionScope
chosen
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
D.
categoryDefinedIn
Indicates that a category is formally specified or established within a particular source, context, or definitional framework.
-
E.
scopeOfSales
Indicates the range, extent, or boundaries within which sales activities, rights, or transactions are valid or permitted.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84db0c48190b2b3d8c5f802f713 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.