Triple
T29938530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRG32k3a generator |
E760432
|
entity |
| Predicate | hasSubstreamCountPerStream |
P195931
|
FINISHED |
| Object | 2^64 substreams (conceptual design) |
—
|
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: 2^64 substreams (conceptual design) | Statement: [MRG32k3a generator, hasSubstreamCountPerStream, 2^64 substreams (conceptual design)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubstreamCountPerStream Context triple: [MRG32k3a generator, hasSubstreamCountPerStream, 2^64 substreams (conceptual design)]
-
A.
hasNumberOfStreams
Indicates the quantity of streams associated with a given entity.
-
B.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
C.
hasStreaming
Indicates that an entity provides or supports streaming access to another entity (such as media, data, or content).
-
D.
hasChannelCount
Indicates that an entity is associated with a specific number of channels.
-
E.
hasShardCount
Indicates that an entity is associated with a specific number of shards into which it is divided or distributed.
- F. None of above. chosen
Provenance (4 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_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
| PDg | Predicate description generation | batch_69fdf5cfa1ec8190b80d887fa1bfb4cf |
completed | May 8, 2026, 2:40 p.m. |
Created at: April 29, 2026, 6:21 p.m.