Triple
T3420041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | standard YouTube license |
E72093
|
entity |
| Predicate | isNonExclusive |
P14581
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [standard YouTube license, isNonExclusive, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonExclusive Context triple: [standard YouTube license, isNonExclusive, yes]
-
A.
nonExclusive
chosen
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
B.
exclusiveTo
Indicates that something is restricted or limited to a specific entity, group, or context and not shared with others.
-
C.
hasExclusiveContractFor
Indicates that one party holds sole contractual rights to provide, use, or represent a specific product, service, or opportunity, excluding all other potential counterparties.
-
D.
isNonCommercial
Indicates that the associated entity, use, or activity is not intended for or involved in commercial, profit-generating purposes.
-
E.
exclusiveProducerOf
Indicates that one entity is the sole producer or manufacturer of another entity, with no other producers involved.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94eb9e8819087a525df4550914b |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.