Triple
T29938502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRG32k3a generator |
E760432
|
entity |
| Predicate | hasCombinationRule |
P2846
|
FINISHED |
| Object | z_n = (x_n - y_n) mod 4294967087 |
—
|
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: z_n = (x_n - y_n) mod 4294967087 | Statement: [MRG32k3a generator, hasCombinationRule, z_n = (x_n - y_n) mod 4294967087]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCombinationRule Context triple: [MRG32k3a generator, hasCombinationRule, z_n = (x_n - y_n) mod 4294967087]
-
A.
allowsCombination
Indicates that one entity permits or supports being combined or used together with another entity.
-
B.
isConsideredCombinationOf
Indicates that something is regarded as being formed by or equivalent to a specific combination of other things or components.
-
C.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
D.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
E.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: April 29, 2026, 6:21 p.m.