Triple
T36468363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stieltjes measure |
E898477
|
entity |
| Predicate | isContinuousOnIntervalsWhere |
P128217
|
FINISHED |
| Object | F is continuous |
—
|
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: F is continuous | Statement: [Stieltjes measure, isContinuousOnIntervalsWhere, F is continuous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContinuousOnIntervalsWhere Context triple: [Stieltjes measure, isContinuousOnIntervalsWhere, F is continuous]
-
A.
isContinuous
chosen
Indicates that a function, process, or relationship changes smoothly without abrupt jumps or breaks over its domain.
-
B.
isContinuously
Indicates that an action, state, or relationship persists without interruption over a period of time.
-
C.
discontinuousAt
Indicates that a function or relation fails to be continuous at a specific point, exhibiting a break, jump, or undefined behavior there.
-
D.
continuityFrom
Indicates that one entity continues, extends, or proceeds directly from another in a seamless or unbroken manner.
-
E.
hasDomainOfDiscontinuity
Indicates that a function or mapping possesses a specific region in its domain where it is not continuous.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:10 p.m.