Triple
T28050991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunn diode |
E708818
|
entity |
| Predicate | hasConductionType |
P200144
|
FINISHED |
| Object | bulk negative differential resistance |
—
|
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: bulk negative differential resistance | Statement: [Gunn diode, hasConductionType, bulk negative differential resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConductionType Context triple: [Gunn diode, hasConductionType, bulk negative differential resistance]
-
A.
conductorType
Indicates the type or category of conductor involved in the relationship or action (e.g., material, role, or functional class).
-
B.
conduction
Indicates the transfer of heat, electricity, or sound through direct contact between interacting entities.
-
C.
conduitType
Indicates the specific kind or category of conduit through which something (such as energy, information, or material) is transmitted or carried.
-
D.
hasConductor
Indicates that an entity (such as an event, performance, or ensemble) is associated with a specific conductor who leads or directs it.
-
E.
hasCALType
Indicates that an entity is associated with a specific CAL (Calendar) type or classification.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69ff779d3d788190af5a2dbc4d7ca3c8 |
completed | May 9, 2026, 6:06 p.m. |
Created at: April 27, 2026, 8:33 p.m.