Triple
T10926906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Fragment Length extension |
E258092
|
entity |
| Predicate | allowsMaxFragmentLength |
P15978
|
FINISHED |
| Object | 512 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: 512 bytes | Statement: [Max Fragment Length extension, allowsMaxFragmentLength, 512 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsMaxFragmentLength Context triple: [Max Fragment Length extension, allowsMaxFragmentLength, 512 bytes]
-
A.
canBeFragmented
Indicates that something is capable of being broken, divided, or split into smaller parts or fragments.
-
B.
maximumSegmentLength
chosen
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
C.
maximumNumberOfSegments
Indicates the greatest allowable or observed count of discrete segments into which something can be or is divided.
-
D.
supportsTagLength
Indicates that an entity is capable of handling or enforcing a specified tag length.
-
E.
numberOfFragmentsApprox
Indicates an approximate count of how many fragments or pieces are associated with the subject.
- 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.