Triple
T1249051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | multinomial theorem |
E26831
|
entity |
| Predicate | proofMethods |
P7024
|
FINISHED |
| Object | induction on 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: induction on n | Statement: [multinomial theorem, proofMethods, induction on n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proofMethods Context triple: [multinomial theorem, proofMethods, induction on n]
-
A.
proved
Indicates that one entity has demonstrated the truth or validity of another entity (such as a statement, theorem, or claim) through logical or evidential means.
-
B.
hasProofMethod
chosen
Indicates that there exists a specific method or technique used to establish or demonstrate the validity of something (such as a statement, claim, or theorem).
-
C.
resolutionMethod
Indicates the specific approach, technique, or process used to resolve a problem, conflict, or issue.
-
D.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
-
E.
standardOfProof
Indicates the level or degree of certainty required to establish that a claim or allegation is true in a given context.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf83b32c81908648e5748b897247 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.