Triple
T1285991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | generalized binomial theorem |
E27434
|
entity |
| Predicate | allowsExponentType |
P26752
|
FINISHED |
| Object | real exponents |
—
|
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: real exponents | Statement: [generalized binomial theorem, allowsExponentType, real exponents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsExponentType Context triple: [generalized binomial theorem, allowsExponentType, real exponents]
-
A.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
B.
expandsPowersOf
Indicates that one entity increases, extends, or enhances the authority, capabilities, or influence held by another entity.
-
C.
allowsConversionTo
Indicates that one entity permits or enables transformation or change into another specified form or state.
-
D.
logarithmBaseDetermines
Indicates that the chosen base of a logarithm determines how a quantity is expressed or scaled in logarithmic terms.
-
E.
exemptionType
Indicates the specific category or kind of exemption that applies in a given context.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b85eb48190a8b61dc397fa6390 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:51 p.m.