Triple
T26971129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopf fibration |
E679319
|
entity |
| Predicate | isVisualizedBy |
P124622
|
FINISHED |
| Object | linked circles in 3-space |
—
|
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: linked circles in 3-space | Statement: [Hopf fibration, isVisualizedBy, linked circles in 3-space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVisualizedBy Context triple: [Hopf fibration, isVisualizedBy, linked circles in 3-space]
-
A.
visualizedIn
Indicates that something is represented or depicted within a particular visual medium, view, or visualization.
-
B.
isDepictedVia
chosen
Indicates that one entity is represented, illustrated, or shown by means of another entity, such as a specific medium, style, or method of depiction.
-
C.
visualDepictionOnScreen
Indicates that one entity is visually shown or rendered on a screen as a depiction of another entity.
-
D.
isObservedIn
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
-
E.
canBeSeenWith
Indicates that two entities are observable together in the same context, setting, or time.
- 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_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:39 a.m.