Triple
T26971110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopf fibration |
E679319
|
entity |
| Predicate | hasTotalSpaceIdentifiedWith |
P168585
|
FINISHED |
| Object | SU(2) |
—
|
NE NERFINISHED |
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: SU(2) | Statement: [Hopf fibration, hasTotalSpaceIdentifiedWith, SU(2)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotalSpaceIdentifiedWith Context triple: [Hopf fibration, hasTotalSpaceIdentifiedWith, SU(2)]
-
A.
totalSpace
Indicates the overall amount of space or capacity available or occupied by an entity or within a given context.
-
B.
hasSecondarySpace
Indicates that an entity possesses or is associated with an additional, subordinate, or auxiliary space beyond its primary one.
-
C.
hasSpaceIn
Indicates that one entity occupies or is contained within a physical or conceptual space provided by another entity.
-
D.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
E.
hasBaseSpace
chosen
Indicates that one entity is defined or structured with respect to another entity that serves as its underlying base space.
- 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_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 6:39 a.m.