Triple
T13389021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxim Integrated |
E319521
|
entity |
| Predicate | notableTechnologyArea |
P19268
|
FINISHED |
| Object | power management |
—
|
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: power management | Statement: [Maxim Integrated, notableTechnologyArea, power management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTechnologyArea Context triple: [Maxim Integrated, notableTechnologyArea, power management]
-
A.
innovationArea
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
B.
technologyField
chosen
Indicates the area or domain of technology in which an entity is involved, specialized, or categorized.
-
C.
notableProgrammingCategory
Indicates that an entity is recognized as belonging to a significant or distinguished category within the domain of programming.
-
D.
notableProjectArea
Indicates that an entity has a significant or distinguished project specifically associated with a particular area or domain.
-
E.
technologySectorFeature
Indicates that something is a characteristic, attribute, or defining aspect of the technology sector.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d3a40081909ba49556130ad0e7 |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.