Triple
T17676604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersenne Twister |
E440656
|
entity |
| Predicate | hasOutputRange |
P27293
|
FINISHED |
| Object | [0, 2^32 − 1] for MT19937 |
—
|
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: [0, 2^32 − 1] for MT19937 | Statement: [Mersenne Twister, hasOutputRange, [0, 2^32 − 1] for MT19937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutputRange Context triple: [Mersenne Twister, hasOutputRange, [0, 2^32 − 1] for MT19937]
-
A.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasOutputType
Indicates that an entity produces, returns, or yields a result of a specified type.
-
C.
hasOutputStructure
Indicates that an entity produces, defines, or is associated with a particular structural form or arrangement as its output.
-
D.
hasOutputStatus
Indicates that an entity is associated with a particular state or condition of its produced output.
-
E.
hasColorRange
Indicates that an entity possesses or is associated with a specific span or set of colors, rather than a single discrete color.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6d9ab88190ab0e25eac8b0101c |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:01 a.m.