Triple
T26971081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopf fibration |
E679319
|
entity |
| Predicate | hasStructureGroup |
P152473
|
FINISHED |
| Object | S^1 |
—
|
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: S^1 | Statement: [Hopf fibration, hasStructureGroup, S^1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureGroup Context triple: [Hopf fibration, hasStructureGroup, S^1]
-
A.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
-
B.
isStructureGroupOf
chosen
Indicates that one entity functions as the structural grouping or organizing framework that encompasses or defines the structure of another entity.
-
C.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
D.
hasStructureLevel
Indicates a relationship where one entity possesses, is assigned, or is characterized by a particular structural level within a hierarchy or layered organization.
-
E.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 6:39 a.m.