Triple
T26408749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RadioGatún |
E663900
|
entity |
| Predicate | usesWordSize |
P44870
|
FINISHED |
| Object | 32-bit words |
—
|
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-bit words | Statement: [RadioGatún, usesWordSize, 32-bit words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWordSize Context triple: [RadioGatún, usesWordSize, 32-bit words]
-
A.
hasWordSize
chosen
Indicates that an entity possesses or is characterized by a specific word length or word-based size.
-
B.
stateSizeBytes
Indicates the size of a given state or stateful data in terms of the number of bytes it occupies.
-
C.
workerSize
Indicates the number of workers or the scale of a workforce associated with an entity.
-
D.
bitWidth
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
E.
usesAllocationBlockSize
Indicates that one entity operates with or depends on a specific allocation block size defined or provided 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:36 p.m.