Triple
T26971101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopf fibration |
E679319
|
entity |
| Predicate | isUsedToShow |
P99577
|
FINISHED |
| Object | π_3(S^2) is nontrivial |
—
|
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: π_3(S^2) is nontrivial | Statement: [Hopf fibration, isUsedToShow, π_3(S^2) is nontrivial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToShow Context triple: [Hopf fibration, isUsedToShow, π_3(S^2) is nontrivial]
-
A.
hasShowUse
chosen
Indicates that something is used or presented as an example or demonstration in a show, display, or illustrative context.
-
B.
isVisibleAs
Indicates that one entity can be perceived or appears to observers under the form, name, or representation of another entity.
-
C.
includesShow
Indicates that one entity contains or features a particular show as part of its content or offerings.
-
D.
requiresShowingBy
Indicates that one entity must be demonstrated, displayed, or presented by another entity as a necessary condition or step.
-
E.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
- 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_69f62124ff1081908d66c2ff35ba5e89 |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:39 a.m.