Triple
T13343080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silent film |
E317871
|
entity |
| Predicate | commonColorTechnique |
P80716
|
FINISHED |
| Object | tinting |
—
|
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: tinting | Statement: [Silent film, commonColorTechnique, tinting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonColorTechnique Context triple: [Silent film, commonColorTechnique, tinting]
-
A.
specialEffectsTechnique
Indicates a relationship where a particular special effects method or process is used to create or enhance visual or auditory effects in a production.
-
B.
colorTreatment
chosen
Indicates that an entity has undergone a process or action that changes, enhances, or assigns its color.
-
C.
renderingTechnology
Indicates the graphics or visualization method used to generate the visual representation of an object, scene, or interface.
-
D.
colorTheory
Indicates a relationship where principles or concepts about how colors interact, combine, or affect perception are applied or referenced between entities.
-
E.
colors
Indicates that one entity assigns, describes, or provides the color or colors of 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8839b48190b164414b418e756c |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.