Triple
T27675150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturm–Liouville problem |
E697758
|
entity |
| Predicate | definedOnInterval |
P4464
|
FINISHED |
| Object | [a,b] |
—
|
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: [a,b] | Statement: [Sturm–Liouville problem, definedOnInterval, [a,b]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedOnInterval Context triple: [Sturm–Liouville problem, definedOnInterval, [a,b]]
-
A.
definedOn
chosen
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
B.
integrationIntervalNotation
Indicates the specific interval notation used to denote the bounds over which an integration is performed.
-
C.
invariantInterval
Indicates that a certain interval or range remains unchanged or constant under a specified transformation or set of conditions.
-
D.
hasIntervalStructure
Indicates that something possesses or is organized according to a specific interval-based structure or pattern.
-
E.
integratesOn
Indicates that one entity is designed to work seamlessly within, or be combined functionally with, another entity or platform.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 2:43 p.m.