Triple
T30041004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMOS |
E763300
|
entity |
| Predicate | fieldEffectType |
P92873
|
FINISHED |
| Object | inversion-mode conduction under gate |
—
|
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: inversion-mode conduction under gate | Statement: [NMOS, fieldEffectType, inversion-mode conduction under gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldEffectType Context triple: [NMOS, fieldEffectType, inversion-mode conduction under gate]
-
A.
tierEffect
Indicates how belonging to a particular tier influences or modifies the outcome, behavior, or properties associated with that tier.
-
B.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
C.
hasTypeOfEffect
chosen
Indicates that one entity produces, exhibits, or is associated with a particular kind or category of effect on another entity or context.
-
D.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
E.
notableEffect
Indicates that one entity has a significant impact, consequence, or influence on another entity or situation.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 6:53 p.m.