Triple
T24894560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNxHR |
E623099
|
entity |
| Predicate | supportsResolutionBeyond |
P33931
|
FINISHED |
| Object | 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: 4K+ | Statement: [DNxHR, supportsResolutionBeyond, 4K+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsResolutionBeyond Context triple: [DNxHR, supportsResolutionBeyond, 4K+]
-
A.
resolvesOver
Indicates that one entity successfully addresses, settles, or overcomes an issue, conflict, or obstacle involving another entity or context.
-
B.
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.
-
C.
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.
-
D.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
E.
resolutionRequires
Indicates that resolving one issue, task, or condition depends on first completing or satisfying another specified prerequisite.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 5:26 a.m.