Triple
T5085192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC5 |
E114618
|
entity |
| Predicate | supportedBlockSizes |
P61205
|
FINISHED |
| Object | 32 bits |
—
|
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: 32 bits | Statement: [RC5, supportedBlockSizes, 32 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedBlockSizes Context triple: [RC5, supportedBlockSizes, 32 bits]
-
A.
blockSize
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
B.
supportsMultiblockAllocation
Indicates that an entity can handle allocating or managing multiple blocks of resources or memory in a single operation.
-
C.
availableDisplaySizes
Indicates the set of display size options that can be provided or used for a given entity.
-
D.
usesAllocationBlockSize
Indicates that one entity operates with or depends on a specific allocation block size defined or provided by another entity.
-
E.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd751db4f4819088b998d7af0e6f41 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73b2c2808190b777e2c2a8a45d3f |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:40 p.m.