Triple
T364222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boltzmann machines |
E7922
|
entity |
| Predicate | approximationMethod |
P4447
|
FINISHED |
| Object | mean-field approximation |
—
|
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: mean-field approximation | Statement: [Boltzmann machines, approximationMethod, mean-field approximation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximationMethod Context triple: [Boltzmann machines, approximationMethod, mean-field approximation]
-
A.
approximationType
chosen
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
B.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
D.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
E.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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_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. |
Created at: Feb. 28, 2026, 1:08 p.m.