Triple
T2912415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abelian group |
E63711
|
entity |
| Predicate | hasMorphism |
P33476
|
FINISHED |
| Object | group homomorphism |
—
|
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: group homomorphism | Statement: [Abelian group, hasMorphism, group homomorphism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMorphism Context triple: [Abelian group, hasMorphism, group homomorphism]
-
A.
hasRelation
chosen
Indicates that there exists some specified relationship or association between two entities.
-
B.
isIsomorphicTo
Indicates that two structures have a one-to-one, structure-preserving correspondence between their elements, making them equivalent in form even if not identical in content.
-
C.
hasVertex
Indicates that an object, typically a geometric shape or graph, includes a specified vertex as one of its corner or node points.
-
D.
hasAxiom
Indicates that an entity is associated with, defined by, or governed through a specific axiom or set of axioms.
-
E.
hasBelyiMap
Indicates that there exists a Belyi map associated with, or defined on, the given mathematical object (typically a curve or surface).
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0eb77708190b745b887f3b9a618 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.