Triple
T364217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boltzmann machines |
E7922
|
entity |
| Predicate | hasPartitionFunction |
P12746
|
FINISHED |
| Object | Z = ∑_s exp(-E(s)) |
—
|
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: Z = ∑_s exp(-E(s)) | Statement: [Boltzmann machines, hasPartitionFunction, Z = ∑_s exp(-E(s))]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartitionFunction Context triple: [Boltzmann machines, hasPartitionFunction, Z = ∑_s exp(-E(s))]
-
A.
hasDistributionFunction
Indicates that an entity is associated with a specific distribution function that characterizes how its values or occurrences are probabilistically or statistically distributed.
-
B.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
C.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebd1016481909b8ba3b047a47145 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eafc8da88190b4a05182f4384442 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.