Triple
T3420011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | standard YouTube license |
E72093
|
entity |
| Predicate | holderRetains |
P6164
|
FINISHED |
| Object | copyright in the video |
—
|
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: copyright in the video | Statement: [standard YouTube license, holderRetains, copyright in the video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderRetains Context triple: [standard YouTube license, holderRetains, copyright in the video]
-
A.
heldForLife
Indicates that something is possessed, controlled, or held by an entity for the entire duration of that entity’s life, without transfer or expiration before death.
-
B.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
C.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
D.
retained
chosen
Indicates that one entity keeps possession, control, or continued engagement of another entity over a period of time.
-
E.
heldEvery
Indicates that an entity consistently possessed or maintained control of another entity throughout every instance or period within a specified range.
- 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.