Triple
T26378118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altera HardCopy family |
E660952
|
entity |
| Predicate | usesDesignSource |
P23439
|
FINISHED |
| Object | FPGA prototype netlist |
—
|
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: FPGA prototype netlist | Statement: [Altera HardCopy family, usesDesignSource, FPGA prototype netlist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDesignSource Context triple: [Altera HardCopy family, usesDesignSource, FPGA prototype netlist]
-
A.
hasDesignInputFrom
Indicates that the design of one entity is based on, influenced by, or derived from input provided by another entity.
-
B.
designedWith
chosen
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
usedDesignDevice
Indicates that one entity employed or operated a particular design-related device or tool.
-
E.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:02 p.m.