Triple
T28901503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Center Stage |
E732962
|
entity |
| Predicate | additionalUseCase |
P158240
|
FINISHED |
| Object | video recordings |
—
|
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: video recordings | Statement: [Center Stage, additionalUseCase, video recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalUseCase Context triple: [Center Stage, additionalUseCase, video recordings]
-
A.
frequentUseCase
Indicates a situation, scenario, or pattern of use that occurs regularly or more often than others in relation to the subject.
-
B.
potentialUse
chosen
Indicates that one entity could be used for, or is suitable for, a particular function, purpose, or application involving another entity.
-
C.
expandedUseOf
Indicates that something is being applied, implemented, or utilized more broadly or extensively than before.
-
D.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa8deec8190b1eef143e10c9598 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:03 a.m.