Triple
T18573023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curie–Weiss law |
E453915
|
entity |
| Predicate | characteristicSignOfTheta |
P662
|
FINISHED |
| Object | positive θ for ferromagnets |
—
|
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: positive θ for ferromagnets | Statement: [Curie–Weiss law, characteristicSignOfTheta, positive θ for ferromagnets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicSignOfTheta Context triple: [Curie–Weiss law, characteristicSignOfTheta, positive θ for ferromagnets]
-
A.
themeCharacteristic
Indicates that a characteristic, quality, or property is attributed to or associated with a particular theme.
-
B.
hasThetaSeries
Indicates that one entity possesses or is associated with a specific theta series related to it.
-
C.
divineSign
Indicates that one entity serves as a supernatural or sacred omen, message, or signal from a divine source to another entity.
-
D.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
E.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543c7f63c81909b5d5764ffd20234 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.