Triple
T33203360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisplayHDR |
E849961
|
entity |
| Predicate | testMethodology |
P43154
|
FINISHED |
| Object | objective, test-based performance metrics |
—
|
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: objective, test-based performance metrics | Statement: [DisplayHDR, testMethodology, objective, test-based performance metrics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testMethodology Context triple: [DisplayHDR, testMethodology, objective, test-based performance metrics]
-
A.
testingMethod
chosen
Indicates the procedure, technique, or approach used to perform a particular test or evaluation.
-
B.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
-
C.
methodologyName
Indicates the specific named method or procedure used or referenced in performing an action or study.
-
D.
describesMethodology
Indicates that one entity explains, specifies, or characterizes the methodology or procedure used by another entity.
-
E.
developedMethodology
Indicates that one entity created, designed, or established a specific methodology used by another entity or in a particular context.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.