Triple
T36454224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirelli DP-L10 |
E898104
|
entity |
| Predicate | basebandChipset |
P20530
|
FINISHED |
| Object | Texas Instruments Calypso family |
—
|
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 Calypso family | Statement: [Pirelli DP-L10, basebandChipset, Texas Instruments Calypso family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basebandChipset Context triple: [Pirelli DP-L10, basebandChipset, Texas Instruments Calypso family]
-
A.
chipset
chosen
Indicates that one entity is the chipset (or is associated with the chipset) used by, contained in, or otherwise functionally related to another entity.
-
B.
chipsetComponent
Indicates that one entity is a hardware component that forms part of, or is integrated into, a particular chipset.
-
C.
chipsetBrand
Indicates the brand or manufacturer associated with a device’s chipset.
-
D.
usedWithChipsetsFrom
Indicates that something is designed or suitable to be used together with specific chipsets from a given manufacturer or family.
-
E.
hasOnChip
Indicates that one component or system includes another component integrated directly onto the same chip or integrated circuit.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.