Triple
T17520580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StandardScaler |
E426669
|
entity |
| Predicate | commonFormula |
P2310
|
FINISHED |
| Object | (x - mean) / standard_deviation |
—
|
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: (x - mean) / standard_deviation | Statement: [StandardScaler, commonFormula, (x - mean) / standard_deviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonFormula Context triple: [StandardScaler, commonFormula, (x - mean) / standard_deviation]
-
A.
recitesFormula
Indicates that one entity verbally or mentally repeats a specific formula, such as a set phrase, equation, or ritual wording, typically from memory.
-
B.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
C.
formulaType
Indicates the specific kind or category of formula associated with an entity or expression.
-
D.
keyFormula
chosen
Indicates that a formula serves as the primary or defining expression associated with an entity or relationship.
-
E.
hasGeneralFormula
Indicates that an entity (such as a class of compounds or expressions) is characterized by a general or canonical formula that represents all its specific instances.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d23cf08190925510344fa36f57 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.