Triple
T25725886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slater-type orbital basis set |
E645113
|
entity |
| Predicate | hasAngularPart |
P35
|
FINISHED |
| Object | spherical harmonic Y_l^m(θ,φ) |
—
|
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: spherical harmonic Y_l^m(θ,φ) | Statement: [Slater-type orbital basis set, hasAngularPart, spherical harmonic Y_l^m(θ,φ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAngularPart Context triple: [Slater-type orbital basis set, hasAngularPart, spherical harmonic Y_l^m(θ,φ)]
-
A.
hasAngularAppearance
Indicates that an entity has a shape or visual form characterized by sharp angles or edges rather than smooth or rounded contours.
-
B.
hasAngularWidth
Indicates that one entity subtends a specified angular width or apparent size as seen from another reference point or observer.
-
C.
hasPart
chosen
Indicates that one entity is a component, segment, or constituent part of another entity.
-
D.
hasTypicalAngle
Indicates that there is a characteristic or commonly occurring angle associated with the relationship between the entities.
-
E.
hasPar
Indicates a relationship where one entity has another entity as its parent.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 10:28 p.m.