Triple
T4975818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mott variable-range hopping |
E111762
|
entity |
| Predicate | relevantAt |
P37
|
FINISHED |
| Object | low temperatures |
—
|
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: low temperatures | Statement: [Mott variable-range hopping, relevantAt, low temperatures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relevantAt Context triple: [Mott variable-range hopping, relevantAt, low temperatures]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
relatedRFC
Indicates that one resource or specification is connected or associated with another through a shared or relevant RFC (Request for Comments) document.
-
E.
relatedTest
Indicates that there exists some form of connection or association between one test and another.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.