Triple
T22438000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bessel functions |
E554675
|
entity |
| Predicate | haveSubClass |
P1244
|
FINISHED |
| Object | integer-order Bessel functions |
—
|
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: integer-order Bessel functions | Statement: [Bessel functions, haveSubClass, integer-order Bessel functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveSubClass Context triple: [Bessel functions, haveSubClass, integer-order Bessel functions]
-
A.
hasMultipleSubclasses
Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
-
B.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
C.
subclassOf
chosen
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
D.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
E.
hasMutableSubclass
Indicates that a class has at least one subclass whose instances can be changed or modified after creation.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15adf52f08190a5b592be3e68af0f |
completed | April 29, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.