Triple
T28050974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunn diode |
E708818
|
entity |
| Predicate | exploitsEffect |
P166195
|
FINISHED |
| Object | Gunn effect |
—
|
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: Gunn effect | Statement: [Gunn diode, exploitsEffect, Gunn effect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploitsEffect Context triple: [Gunn diode, exploitsEffect, Gunn effect]
-
A.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
B.
exploitsFeature
chosen
Indicates that one entity takes advantage of or leverages a particular feature or capability of another entity.
-
C.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
-
D.
providesEffect
Indicates that one entity causes, delivers, or produces a particular effect or outcome on another entity.
-
E.
isExploitedFor
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
- 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_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 8:33 p.m.