Triple
T34545633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantor normal form |
E886917
|
entity |
| Predicate | exponentType |
P179301
|
FINISHED |
| Object | ordinals |
—
|
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: ordinals | Statement: [Cantor normal form, exponentType, ordinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exponentType Context triple: [Cantor normal form, exponentType, ordinals]
-
A.
exponent
Indicates that one quantity is raised to the power of another, expressing repeated multiplication of a base by itself.
-
B.
allowsExponentType
Indicates that one entity permits or supports the use of a specified type for an exponent in an operation or expression.
-
C.
typicalExponent
Indicates that one quantity serves as the characteristic or standard exponent associated with another quantity or expression.
-
D.
baseOfExponentialTerm
Indicates that one quantity serves as the base in an exponential expression or term involving another quantity as the exponent.
-
E.
notableExponents
Indicates that certain entities are especially prominent, influential, or exemplary practitioners or representatives of a given field, movement, or activity.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7201fc32c8190a79a85a7a4f63662 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:02 a.m.