Triple
T33320257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stiefel–Whitney classes |
E853116
|
entity |
| Predicate | degreeOf |
P95385
|
FINISHED |
| Object | w_i(E) has degree i |
—
|
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: w_i(E) has degree i | Statement: [Stiefel–Whitney classes, degreeOf, w_i(E) has degree i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: degreeOf Context triple: [Stiefel–Whitney classes, degreeOf, w_i(E) has degree i]
-
A.
isDegreeOf
Indicates that one entity is an academic or professional degree held, pursued, or associated with another entity.
-
B.
имеетСтепень
Indicates that one entity possesses or has been awarded a certain academic or professional degree in relation to another entity.
-
C.
degreeOver
Indicates that one entity’s degree, level, or extent exceeds that of another entity.
-
D.
notionOfDegree
chosen
Indicates a relationship where one entity specifies or characterizes the degree, intensity, or extent to which a property or condition applies to another entity.
-
E.
degreeFamily
Indicates a family relationship defined through academic or educational degrees (e.g., people connected by shared or related degrees).
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.