Triple
T31498114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-Cinetone |
E803603
|
entity |
| Predicate | highlightHandling |
P56319
|
FINISHED |
| Object | gentle highlight roll-off |
—
|
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: gentle highlight roll-off | Statement: [S-Cinetone, highlightHandling, gentle highlight roll-off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlightHandling Context triple: [S-Cinetone, highlightHandling, gentle highlight roll-off]
-
A.
highlightsSign
Indicates that one entity visually emphasizes or draws special attention to a sign.
-
B.
handlingProperty
chosen
Indicates that one entity specifies how another entity should be handled, processed, or treated under certain conditions.
-
C.
handles
Indicates that one entity is responsible for dealing with, managing, or taking care of another entity or task.
-
D.
handledIn
Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
-
E.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:42 p.m.