Triple
T19231132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernstein polynomials |
E480872
|
entity |
| Predicate | hasEndpointValue |
P18302
|
FINISHED |
| Object | B_{n,0}(0) = 1 |
—
|
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: B_{n,0}(0) = 1 | Statement: [Bernstein polynomials, hasEndpointValue, B_{n,0}(0) = 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndpointValue
Context triple: [Bernstein polynomials, hasEndpointValue, B_{n,0}(0) = 1]
-
A.
hasEndpointType
Indicates that an entity has a specific type or classification assigned to one of its endpoints.
-
B.
hasValue
chosen
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
C.
hasEndpointCity
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
-
D.
hasEndpointStation
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
E.
isKeyEndpointOf
Indicates that one endpoint in a connection, link, or structure serves as the primary or designated key endpoint of the other.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9ce5e081909df994841ce476d5 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:25 p.m.