Triple
T19376970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V2O3 |
E484696
|
entity |
| Predicate | bandGapInInsulatingPhase |
P135713
|
FINISHED |
| Object | small Mott gap |
—
|
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: small Mott gap | Statement: [V2O3, bandGapInInsulatingPhase, small Mott gap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandGapInInsulatingPhase Context triple: [V2O3, bandGapInInsulatingPhase, small Mott gap]
-
A.
bandGapType
Indicates the type or nature of the band gap (e.g., direct or indirect) characterizing the electronic transition behavior between energy bands.
-
B.
bandgapEngineeredBy
Indicates that the bandgap of a material or structure has been intentionally modified or tailored through a specific method, process, or design technique.
-
C.
hasPhaseTransition
Indicates that an entity undergoes or exhibits a change from one physical phase or state of matter to another.
-
D.
typeOfGap
Indicates the specific kind or category of gap that exists between or within entities.
-
E.
hasRingGap
Indicates that there is a discontinuity or missing segment in a ring-like structure or arrangement between the related entities.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5cfbf48190ac60e3ffa6baa263 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:35 p.m.