Triple
T36454116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Instruments Calypso-based phones |
E898102
|
entity |
| Predicate | commonVendors |
P99393
|
FINISHED |
| Object | Motorola |
—
|
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: Motorola | Statement: [Texas Instruments Calypso-based phones, commonVendors, Motorola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonVendors Context triple: [Texas Instruments Calypso-based phones, commonVendors, Motorola]
-
A.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
B.
eligibleVendors
Indicates that certain vendors meet the required criteria or conditions to be considered eligible for a specified purpose or process.
-
C.
dataVendor
Indicates a relationship where one entity serves as a provider or supplier of data to another entity.
-
D.
technologyVendor
Indicates that one entity serves as the provider or supplier of technology products or services to another entity.
-
E.
commonVendorSupport
chosen
Indicates that two entities are both supported by, or compatible with, at least one of the same vendors.
- 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_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:10 p.m.