Triple
T21091753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Protocol fragmentation and reassembly |
E519653
|
entity |
| Predicate | usesExtensionHeader |
P96691
|
FINISHED |
| Object | IPv6 Fragment header |
—
|
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: IPv6 Fragment header | Statement: [Internet Protocol fragmentation and reassembly, usesExtensionHeader, IPv6 Fragment header]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExtensionHeader Context triple: [Internet Protocol fragmentation and reassembly, usesExtensionHeader, IPv6 Fragment header]
-
A.
hasExtensionBy
Indicates that one entity is extended, augmented, or further developed by another entity.
-
B.
supportsExtensionsFrom
Indicates that one entity is capable of recognizing, loading, or interoperating with extensions originating from another entity.
-
C.
usesExtensionOf
Indicates that one entity makes use of another entity that is an extension or extended version of something else.
-
D.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
E.
includesExtension
chosen
Indicates that one entity contains or incorporates another entity as an added or supplementary extension.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:51 p.m.