Triple
T36877079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurewicz homomorphism |
E911367
|
entity |
| Predicate | targetStructure |
P199096
|
FINISHED |
| Object | abelian group H_n(X) |
—
|
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: abelian group H_n(X) | Statement: [Hurewicz homomorphism, targetStructure, abelian group H_n(X)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetStructure Context triple: [Hurewicz homomorphism, targetStructure, abelian group H_n(X)]
-
A.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
B.
topStructure
Indicates that one structure occupies the highest or most superior position relative to other structures within a given system or hierarchy.
-
C.
laterStructureType
Indicates that one structure is of a type that occurs or is instantiated later than another structure in a temporal or sequential sense.
-
D.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
E.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
| PDg | Predicate description generation | batch_69ff1e3d5f488190ba6e4f024128fb99 |
completed | May 9, 2026, 11:45 a.m. |
Created at: May 3, 2026, 4:13 p.m.