Triple
T15502467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khinchin's law of the iterated logarithm |
E378993
|
entity |
| Predicate | isFormulatedFor |
P9494
|
FINISHED |
| Object | partial sums S_n = X_1 + ... + X_n |
—
|
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: partial sums S_n = X_1 + ... + X_n | Statement: [Khinchin's law of the iterated logarithm, isFormulatedFor, partial sums S_n = X_1 + ... + X_n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormulatedFor Context triple: [Khinchin's law of the iterated logarithm, isFormulatedFor, partial sums S_n = X_1 + ... + X_n]
-
A.
isFormulatedUsing
Indicates that something is created, defined, or expressed by means of a specified method, material, or set of components.
-
B.
coFormulatedWith
Indicates that one entity is formulated together with another as part of the same combined product or composition.
-
C.
formulatedIn
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
-
D.
coFormulated
Indicates that two or more entities were jointly formulated, designed, or created together as part of the same process or product.
-
E.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcc5bb88190b8a9a81419a9a38b |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:54 a.m.