Triple
T24805866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newton interpolation polynomial |
E620656
|
entity |
| Predicate | usesSequence |
P161421
|
FINISHED |
| Object | nodes x_0, x_1, ..., x_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: nodes x_0, x_1, ..., x_n | Statement: [Newton interpolation polynomial, usesSequence, nodes x_0, x_1, ..., x_n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSequence Context triple: [Newton interpolation polynomial, usesSequence, nodes x_0, x_1, ..., x_n]
-
A.
isSequence
Indicates that one entity is an ordered list or succession of elements arranged in a specific, meaningful order.
-
B.
isSequenceOf
Indicates that one entity occurs in a specific order directly following or as part of an ordered list relative to another entity.
-
C.
usesSequentialPassages
Indicates that one entity employs or organizes content in a series of passages that follow a specific sequential order.
-
D.
sequenceWith
Indicates that one entity occurs in a specific order directly before or after another entity as part of a defined sequence.
-
E.
sequenceInWork
Indicates that one work appears as a sequential part or installment within a larger overarching work.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 18, 2026, 4:50 a.m.