Triple
T8470813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datagram Delivery Protocol |
E200274
|
entity |
| Predicate | headerFields |
P3703
|
FINISHED |
| Object | source address |
—
|
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: source address | Statement: [Datagram Delivery Protocol, headerFields, source address]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerFields Context triple: [Datagram Delivery Protocol, headerFields, source address]
-
A.
headerField
chosen
Indicates that one entity is a specific header field (such as a name–value pair) belonging to or defined within another entity, typically a message, request, or document header.
-
B.
headerSize
Indicates the size or length of a header associated with an entity or data structure.
-
C.
holderField
Indicates that a specified field or attribute belongs to, is maintained by, or is associated with a particular holder entity.
-
D.
bearerField
Indicates that one entity serves as the bearer or holder of a specific field, attribute, or property associated with another entity.
-
E.
headerFile
Indicates that one file serves as a header file for another file, typically declaring interfaces, types, or constants used by that other file.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.