Triple

T36870514
Position Surface form Disambiguated ID Type / Status
Subject 4-sphere S^4 E911210 entity
Predicate homologyGroupH_2 P187109 FINISHED
Object 0 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: 0 | Statement: [4-sphere S^4, homologyGroupH_2, 0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: homologyGroupH_2
Context triple: [4-sphere S^4, homologyGroupH_2, 0]
  • A. homologyGroupH_1
    Indicates that the first homology group (H₁) relates spaces or objects by capturing their one-dimensional holes or cycles up to equivalence.
  • B. homologyGroupH_0
    Indicates that the relationship captures the zeroth homology group, describing how connected components of a topological space are organized in algebraic terms.
  • C. hasHomotopyGroup
    Indicates that one topological space has a specified homotopy group (of a given degree) related to its structure of continuous deformations.
  • D. homotopyType
    Indicates that two topological spaces or maps share the same homotopy type, meaning they can be continuously deformed into one another up to homotopy.
  • E. fundamentalGroup
    Indicates the relationship that assigns to a topological space its fundamental group, capturing how loops in the space can be continuously deformed into one another.
  • F. None of above. chosen

Provenance (4 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_69f76e80f6f0819091cba8e19b269615 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb3425666081908916fcbf3b5dd907 completed May 6, 2026, 12:29 p.m.
PD Predicate disambiguation batch_69fb2f5f3164819099429c2cc3d24e01 completed May 6, 2026, 12:09 p.m.
PDg Predicate description generation batch_69fb3424724c8190ba55ecf66fa0b171 completed May 6, 2026, 12:29 p.m.
Created at: May 3, 2026, 4:13 p.m.