Triple
T26136311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ion Torrent |
E659392
|
entity |
| Predicate | hasChipType |
P168049
|
FINISHED |
| Object | Ion 314 chip |
—
|
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: Ion 314 chip | Statement: [Ion Torrent, hasChipType, Ion 314 chip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChipType Context triple: [Ion Torrent, hasChipType, Ion 314 chip]
-
A.
hasOnChip
Indicates that one component or system includes another component integrated directly onto the same chip or integrated circuit.
-
B.
hasMICType
Indicates that an entity is associated with a specific Market Identifier Code (MIC) classification type.
-
C.
requiresSupportChips
Indicates that an entity depends on or needs additional support components (chips) in order to function or be used properly.
-
D.
supportsOnChipNetworking
Indicates that one entity provides or enables integrated networking capabilities directly on a chip for another entity.
-
E.
hasOnChipMMUVariantName
Indicates that an entity has a specific named variant of an on-chip Memory Management Unit (MMU) associated with it.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 26, 2026, 8:17 p.m.