Triple
T27343765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conexant Systems |
E684175
|
entity |
| Predicate | keyApplicationDomain |
P163098
|
FINISHED |
| Object | digital set‑top boxes |
—
|
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: digital set‑top boxes | Statement: [Conexant Systems, keyApplicationDomain, digital set‑top boxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyApplicationDomain Context triple: [Conexant Systems, keyApplicationDomain, digital set‑top boxes]
-
A.
keyApplication
Indicates that an application or software program serves as the primary or central tool used for a particular purpose or function.
-
B.
originalApplicationDomain
Indicates the domain or field in which something was first designed, intended, or primarily applied.
-
C.
keyHub
Indicates a central or primary element that connects, coordinates, or controls multiple related components or interactions.
-
D.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
E.
defaultDomain
Indicates that one entity serves as the standard or primary domain associated with another entity, used when no more specific domain is specified.
- F. None of above. chosen
Provenance (4 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 11:44 a.m.