Triple
T29181759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI OMAP3430 |
E739762
|
entity |
| Predicate | hasISP |
P169303
|
FINISHED |
| Object | integrated image signal processor |
—
|
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: integrated image signal processor | Statement: [TI OMAP3430, hasISP, integrated image signal processor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISP Context triple: [TI OMAP3430, hasISP, integrated image signal processor]
-
A.
hasIP
Indicates that one entity possesses, is assigned, or is associated with a specific IP address.
-
B.
integratesISP
Indicates that one entity incorporates or connects with an Internet Service Provider (ISP) to enable or enhance network or internet-related functionality.
-
C.
hasNet
Indicates that one entity possesses, is equipped with, or includes a net.
-
D.
usesIP
Indicates that one entity makes use of, operates through, or is associated with a particular IP address.
-
E.
integratedISP
Indicates that an entity has an Internet Service Provider function that is built into or bundled with it, rather than relying on an external ISP.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 28, 2026, 11:57 a.m.