Triple
T21047012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | affine group of R^n |
E518474
|
entity |
| Predicate | hasMultiplicationRule |
P71174
|
FINISHED |
| Object | (A,b)(C,d) = (AC, A d + b) |
—
|
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: (A,b)(C,d) = (AC, A d + b) | Statement: [affine group of R^n, hasMultiplicationRule, (A,b)(C,d) = (AC, A d + b)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultiplicationRule Context triple: [affine group of R^n, hasMultiplicationRule, (A,b)(C,d) = (AC, A d + b)]
-
A.
hasMultiplicationFormula
chosen
Indicates that there exists a specific multiplication-based formula or rule that defines or computes the value or behavior of the related entity.
-
B.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
D.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
-
E.
hasDivisionRule
Indicates that one entity is governed, organized, or separated according to a specified rule or method of division defined by another entity.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf4d26481908b639996500a8319 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.