Triple
T25726203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian |
E645120
|
entity |
| Predicate | supportsCalculation |
P187024
|
FINISHED |
| Object | geometry optimization |
—
|
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: geometry optimization | Statement: [Gaussian, supportsCalculation, geometry optimization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCalculation Context triple: [Gaussian, supportsCalculation, geometry optimization]
-
A.
supportsCalculator
Indicates that one entity provides compatibility with or the ability to run or use a calculator feature for another entity.
-
B.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
-
C.
calculationType
Indicates the specific method, formula, or approach used to perform a calculation in the described relationship.
-
D.
calculationProvider
Indicates that one entity serves as the source or performer of a calculation for another entity or process.
-
E.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: April 21, 2026, 11:04 p.m.