Triple
T575567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTube Stories |
E13753
|
entity |
| Predicate | contentPersistence |
P11419
|
FINISHED |
| Object | temporary |
—
|
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: temporary | Statement: [YouTube Stories, contentPersistence, temporary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentPersistence Context triple: [YouTube Stories, contentPersistence, temporary]
-
A.
persistence
chosen
Indicates a continued or repeated existence, occurrence, or effort of something over time despite potential changes or obstacles.
-
B.
save
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
-
C.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
D.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
E.
retained
Indicates that one entity keeps possession, control, or continued engagement of another entity over a period of time.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b67395c8190a8046ff7debe9d1f |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.