Triple
T34545637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantor normal form |
E886917
|
entity |
| Predicate | standardFormFor |
P158574
|
FINISHED |
| Object | ordinal arithmetic |
—
|
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: ordinal arithmetic | Statement: [Cantor normal form, standardFormFor, ordinal arithmetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardFormFor Context triple: [Cantor normal form, standardFormFor, ordinal arithmetic]
-
A.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
B.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
-
C.
standardFormBasedOn
Indicates that one entity’s standard or canonical form is derived from, defined by, or constructed on the basis of another entity.
-
D.
standardFormBasedIn
Indicates that a standardized form or format is established, defined, or grounded in a particular source, basis, or reference framework.
-
E.
standardizedFormOf
chosen
Indicates that one entity is the normalized or officially standardized version of another, often consolidating variations or alternative forms into a single canonical form.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 2:02 a.m.