Triple
T10773194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grothendieck group |
E254131
|
entity |
| Predicate | hasCanonicalMapType |
P42815
|
FINISHED |
| Object | monoid 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: monoid homomorphism | Statement: [Grothendieck group, hasCanonicalMapType, monoid homomorphism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalMapType Context triple: [Grothendieck group, hasCanonicalMapType, monoid homomorphism]
-
A.
hasMapType
chosen
Indicates that one entity is associated with a specific type or category of map.
-
B.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
-
C.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
D.
hasCanonicalAspect
Indicates that an entity is associated with its standard or officially recognized aspect, form, or representation.
-
E.
hasCanonicalContext
Indicates that something is associated with its primary, standard, or officially recognized contextual setting or framework.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7329b27748190bd0e2569c7972fd1 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.