Triple
T36876993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bockstein homomorphism |
E911365
|
entity |
| Predicate | usedWithCoefficients |
P93936
|
FINISHED |
| Object | Z/nZ |
—
|
NE NERFINISHED |
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: Z/nZ | Statement: [Bockstein homomorphism, usedWithCoefficients, Z/nZ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithCoefficients Context triple: [Bockstein homomorphism, usedWithCoefficients, Z/nZ]
-
A.
coefficientsIn
chosen
Indicates that one entity appears as a coefficient within the mathematical expression or representation of another entity.
-
B.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
C.
holdsWithCoefficients
Indicates that a relationship or equation remains valid when specific numerical coefficients are applied to its terms.
-
D.
conditionOnCoefficients
Indicates that one entity’s state, validity, or behavior is determined by or contingent upon the values of certain coefficients.
-
E.
coefficientProperty
Indicates a relationship where one entity serves as a coefficient or scalar factor that quantitatively modifies or characterizes another entity or property.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.