Triple
T1036780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Planet |
E22379
|
entity |
| Predicate | usesCinematographyTechnique |
P2760
|
FINISHED |
| Object | ultra high definition 4K |
—
|
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: ultra high definition 4K | Statement: [Our Planet, usesCinematographyTechnique, ultra high definition 4K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCinematographyTechnique Context triple: [Our Planet, usesCinematographyTechnique, ultra high definition 4K]
-
A.
filmingTechnique
chosen
Indicates the specific method or style used to capture visual content during the filming process.
-
B.
cinematographyBy
Indicates that the cinematographic work (such as the camera work or visual style of a film or video) is created or supervised by a specified person or entity.
-
C.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
D.
observingTechnique
Indicates the method or procedure used to carry out an observation.
-
E.
artisticTechnique
Indicates the method, style, or process used to create or execute an artistic work.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.