Triple
T38369879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Channel 101 |
E892547
|
entity |
| Predicate | curationPolicy |
P10263
|
FINISHED |
| Object | open submissions |
—
|
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: open submissions | Statement: [Channel 101, curationPolicy, open submissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curationPolicy Context triple: [Channel 101, curationPolicy, open submissions]
-
A.
collectionPolicy
chosen
Indicates the rules or guidelines that govern how items are gathered, selected, and managed within a collection.
-
B.
curationType
Indicates the specific manner or method by which something has been selected, organized, or managed within a curated collection or context.
-
C.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
D.
editingPolicy
Indicates that one entity defines or enforces the rules, constraints, or procedures governing how another entity may be edited or modified.
-
E.
currentPolicy
Indicates that a given policy is the one presently in effect or actively governing the relevant context.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.