Triple
T6111138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peierls transition |
E136241
|
entity |
| Predicate | changesProperty |
P68214
|
FINISHED |
| Object | electrical conductivity |
—
|
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: electrical conductivity | Statement: [Peierls transition, changesProperty, electrical conductivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changesProperty Context triple: [Peierls transition, changesProperty, electrical conductivity]
-
A.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
B.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
C.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
D.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
E.
changedOn
Indicates that an entity underwent a modification or update at a specific point in time.
- 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bbbbea88190b889a7c30af1d71a |
completed | March 22, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:13 p.m.