Triple
T1389448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noetherian induction |
E29920
|
entity |
| Predicate | usedToProve |
P21917
|
FINISHED |
| Object | termination of algorithms |
—
|
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: termination of algorithms | Statement: [Noetherian induction, usedToProve, termination of algorithms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToProve Context triple: [Noetherian induction, usedToProve, termination of algorithms]
-
A.
proved
chosen
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.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
E.
usedToInfer
Indicates that one entity serves as a basis or source from which another entity is logically derived or concluded.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35ce48c81909aaad7dfa2df63fa |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.