Triple
T36468312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newton–Cotes formulas |
E898476
|
entity |
| Predicate | closedFormulasUse |
P191728
|
FINISHED |
| Object | nodes including both endpoints |
—
|
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: nodes including both endpoints | Statement: [Newton–Cotes formulas, closedFormulasUse, nodes including both endpoints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedFormulasUse Context triple: [Newton–Cotes formulas, closedFormulasUse, nodes including both endpoints]
-
A.
openFormulasUse
Indicates that one entity makes use of or depends on open (i.e., not fully instantiated or closed) logical formulas associated with another entity.
-
B.
closingFormula
Indicates the conventional closing phrase or formula used to end a communication, such as a letter, email, or message.
-
C.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
D.
closureUse
Indicates that one entity uses or captures another entity within a closure context (such as a variable or resource referenced by a closure).
-
E.
closureUse
Indicates that one entity makes use of another entity within a closure, typically capturing it from an enclosing scope for later execution.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 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. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:10 p.m.