Triple
T26971004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander–Spanier cohomology |
E679316
|
entity |
| Predicate | coefficientVariable |
P93936
|
FINISHED |
| Object | abelian group G |
—
|
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 G | Statement: [Alexander–Spanier cohomology, coefficientVariable, abelian group G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coefficientVariable Context triple: [Alexander–Spanier cohomology, coefficientVariable, abelian group G]
-
A.
coefficientProperty
Indicates a relationship where one entity serves as a coefficient or scalar factor that quantitatively modifies or characterizes another entity or property.
-
B.
coefficientSystems
Indicates a relationship where specific numerical or algebraic coefficients are assigned or associated with a system, structure, or set of elements.
-
C.
coefficientsIn
chosen
Indicates that one entity appears as a coefficient within the mathematical expression or representation of another entity.
-
D.
conjugateVariable
Indicates that one variable is the conjugate counterpart of another, typically related by a conjugation operation such as complex, algebraic, or canonical conjugation.
-
E.
coordinateVariables
Indicates that the variables are aligned or paired together in a shared coordinate system or structured correspondence.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62124ff1081908d66c2ff35ba5e89 |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:39 a.m.