Triple

T37480137
Position Surface form Disambiguated ID Type / Status
Subject Rec. BT.2020 E931390 entity
Predicate definesResolution P33931 FINISHED
Object 3840×2160 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: 3840×2160 | Statement: [Rec. BT.2020, definesResolution, 3840×2160]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesResolution
Context triple: [Rec. BT.2020, definesResolution, 3840×2160]
  • A. resolutionOf
    Indicates that one entity is the formal decision, outcome, or solution produced in response to, or for the purpose of addressing, another entity such as an issue, proposal, or problem.
  • B. describesResolution
    Indicates that one entity specifies or provides details about the resolution or level of detail of another entity.
  • C. resolutionDeterminedBy
    Indicates that the outcome or level of resolution of one entity is decided, defined, or constrained by another entity.
  • D. resolutionClass
    Indicates the category or type of resolution applied to address or conclude a particular issue, conflict, or process.
  • E. hasResolution chosen
    Indicates that one entity possesses, specifies, or is associated with a particular level or type of resolution (such as detail, clarity, or granularity) in relation to 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_69f76ec382248190b47844df596123c6 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fefa064ab48190925759950d0d94d9 completed May 9, 2026, 9:10 a.m.
PD Predicate disambiguation batch_69fef96ae5d08190b027435753c44821 completed May 9, 2026, 9:07 a.m.
Created at: May 3, 2026, 4:17 p.m.