Triple
T35598755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM10 operational amplifier |
E1028707
|
entity |
| Predicate | datasheetPublisher |
P121322
|
FINISHED |
| Object | Texas Instruments |
—
|
NE NERFINISHED |
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: Texas Instruments | Statement: [LM10 operational amplifier, datasheetPublisher, Texas Instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datasheetPublisher Context triple: [LM10 operational amplifier, datasheetPublisher, Texas Instruments]
-
A.
dataPublication
Indicates that some data has been made publicly available or formally released, typically through a defined dissemination or publishing process.
-
B.
openSpecificationPublishedBy
Indicates that an open specification has been formally published or issued by a particular entity.
-
C.
digitalPublisher
chosen
Indicates the entity that is responsible for publishing the resource in a digital format.
-
D.
documentationPublishedOn
Indicates that documentation was made publicly available or officially released on a specific date or at a specific time.
-
E.
DOCProduct
Indicates a relationship where an entity is the product or outcome documented or produced in a particular document or documentation process.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.