Triple
T26971091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopf fibration |
E679319
|
entity |
| Predicate | hasDimensionOfFiber |
P179304
|
FINISHED |
| Object | 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: 1 | Statement: [Hopf fibration, hasDimensionOfFiber, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDimensionOfFiber Context triple: [Hopf fibration, hasDimensionOfFiber, 1]
-
A.
genericFiberDimension
chosen
Indicates the dimension of a typical (generic) fiber in a family of morphisms or maps, describing how many independent directions the fibers usually have over most points of the base.
-
B.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
C.
hasDimensionality
Indicates that an entity possesses a specific number of dimensions or a particular dimensional structure.
-
D.
hasIndividualDimension
Indicates that an entity possesses a specific, separately identifiable dimension or measurable extent as an individual attribute.
-
E.
cardinalityOfFibers
Indicates the number of distinct fibers (preimage sets) associated with a given mapping or relation.
- 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_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 6:39 a.m.