Triple
T28050932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | resonant tunneling diode |
E708817
|
entity |
| Predicate | hasI-VCharacteristic |
P274
|
FINISHED |
| Object | N-shaped |
—
|
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: N-shaped | Statement: [resonant tunneling diode, hasI-VCharacteristic, N-shaped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasI-VCharacteristic Context triple: [resonant tunneling diode, hasI-VCharacteristic, N-shaped]
-
A.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
hasThermalCharacteristic
Indicates that an entity possesses a specific thermal property or behavior, such as conductivity, capacity, or response to temperature.
-
C.
hasCharacteristicArtifact
Indicates that an entity is associated with a specific artifact that characterizes, exemplifies, or is typical of it.
-
D.
hasImpedance
Indicates that one entity possesses or is characterized by a specific electrical impedance value or property in relation to another.
-
E.
hasInversionCapability
Indicates that an entity possesses the ability to reverse or invert another entity, state, or process.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd945f08190b2526b01686a1562 |
completed | May 2, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:33 p.m.