Triple
T8918172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celluloid |
E212344
|
entity |
| Predicate | supportsVideoPlayback |
P86386
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Celluloid, supportsVideoPlayback, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVideoPlayback Context triple: [Celluloid, supportsVideoPlayback, true]
-
A.
supportsVerticalVideo
Indicates that one entity provides compatibility with or proper handling of vertical (portrait-oriented) video content for another entity.
-
B.
supportsRemotePlay
Indicates that one entity enables or is compatible with remote play functionality for another entity.
-
C.
supportsHEVC
Indicates that one entity provides compatibility with or the ability to handle HEVC (High Efficiency Video Coding) for another entity.
-
D.
supportsVideoLengthRange
Indicates that an entity is compatible with or allows videos whose durations fall within a specified minimum-to-maximum time range.
-
E.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
- F. None of above. chosen
Provenance (4 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.