Triple
T286781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFTP |
E5902
|
entity |
| Predicate | blockSizeDefault |
P3276
|
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: [TFTP, blockSizeDefault, 512 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockSizeDefault Context triple: [TFTP, blockSizeDefault, 512 bytes]
-
A.
fieldSize
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
B.
packetSize
chosen
Indicates the size or amount of data contained in a packet within a communication or data transfer context.
-
C.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
D.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
E.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.