Triple
T19377051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sr2CuO2Cl2 |
E484698
|
entity |
| Predicate | isChargeTransferInsulator |
P135722
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sr2CuO2Cl2, isChargeTransferInsulator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isChargeTransferInsulator Context triple: [Sr2CuO2Cl2, isChargeTransferInsulator, true]
-
A.
isInterchange
Indicates that two entities can be substituted or exchanged for one another without affecting the relevant system, function, or outcome.
-
B.
containsCharge
Indicates that one entity includes, holds, or encompasses a specific charge associated with it.
-
C.
isColorCharged
Indicates that an entity possesses color charge, meaning it carries the type of charge associated with the strong nuclear interaction in quantum chromodynamics.
-
D.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
E.
isInterchangeBetween
Indicates a relationship where something serves as a point or medium through which two or more entities can exchange or transfer items, information, or traffic between each other.
- 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.