Triple
T33203351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisplayHDR |
E849961
|
entity |
| Predicate | industryAdoption |
P18342
|
FINISHED |
| Object | PC monitor manufacturers |
—
|
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: PC monitor manufacturers | Statement: [DisplayHDR, industryAdoption, PC monitor manufacturers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryAdoption Context triple: [DisplayHDR, industryAdoption, PC monitor manufacturers]
-
A.
marketAdoption
chosen
Indicates the extent to which a product, service, or innovation has been accepted and used by its target market or customer base.
-
B.
industryApproach
Indicates the method, strategy, or way in which an industry addresses, handles, or engages with a particular subject or activity.
-
C.
industryStart
Indicates the point in time or event at which an industry, industrial activity, or industrial era begins.
-
D.
industryTransformed
Indicates that an entity has fundamentally changed the structure, practices, or dynamics of a particular industry.
-
E.
industryStatus
Indicates the current operational or regulatory condition of an entity within its industry (e.g., active, inactive, regulated, or restricted status).
- 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_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:30 a.m.