Triple
T36640586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S5 |
E904571
|
entity |
| Predicate | hasSignHomomorphismTo |
P69858
|
FINISHED |
| Object | C2 |
—
|
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: C2 | Statement: [S5, hasSignHomomorphismTo, C2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignHomomorphismTo Context triple: [S5, hasSignHomomorphismTo, C2]
-
A.
hasHomomorphism
chosen
Indicates that there exists a structure-preserving map (homomorphism) from one mathematical structure to another.
-
B.
hasCohomologyIsomorphicTo
Indicates that the cohomology groups (with their algebraic structure) of one object are isomorphic to those of another object.
-
C.
hasHomotopyGroup
Indicates that one topological space has a specified homotopy group (of a given degree) related to its structure of continuous deformations.
-
D.
hasMorphismsCorrespondingTo
Indicates that there exist morphisms between two structures such that they correspond in a specified way (e.g., via a functor, equivalence, or structural mapping) according to the given context.
-
E.
hasAutomorphismGroupContaining
Indicates that the automorphism group of one mathematical structure includes the other group as a subgroup or component.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:11 p.m.