Triple
T10926904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Fragment Length extension |
E258092
|
entity |
| Predicate | defaultRecordSizeWithoutExtension |
P21839
|
FINISHED |
| Object | 2^14 bytes |
—
|
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^14 bytes | Statement: [Max Fragment Length extension, defaultRecordSizeWithoutExtension, 2^14 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultRecordSizeWithoutExtension Context triple: [Max Fragment Length extension, defaultRecordSizeWithoutExtension, 2^14 bytes]
-
A.
defaultSizeAlgorithm
Indicates the method or procedure used to determine an entity’s size when no explicit size is specified.
-
B.
stateSizeBytes
chosen
Indicates the size of a given state or stateful data in terms of the number of bytes it occupies.
-
C.
minimumFrameSize
Indicates the smallest allowable or supported size of a frame in the given context or system.
-
D.
fieldSize
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
E.
signatureSize
Indicates the size or length of a given signature, typically measured in bytes or characters.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709165188190aa30dd08deddade4 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.