Triple
T13443933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolmogorov axioms |
E320431
|
entity |
| Predicate | acceptedAs |
P58404
|
FINISHED |
| Object | standard axioms of probability |
—
|
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: standard axioms of probability | Statement: [Kolmogorov axioms, acceptedAs, standard axioms of probability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptedAs Context triple: [Kolmogorov axioms, acceptedAs, standard axioms of probability]
-
A.
acceptedFor
Indicates that one entity has been approved or admitted to receive, participate in, or be associated with another entity.
-
B.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
C.
acceptedAt
Indicates the time or event at which something (such as a request, submission, or offer) is formally accepted.
-
D.
approvedAs
chosen
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
E.
approvedAt
Indicates the date and time at which an entity received formal approval.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee881888190811ddf01bc699864 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.