Triple
T8904610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetBulk operation |
E212021
|
entity |
| Predicate | pduTypeCode |
P70469
|
FINISHED |
| Object | GetBulkRequest-PDU |
—
|
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: GetBulkRequest-PDU | Statement: [GetBulk operation, pduTypeCode, GetBulkRequest-PDU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pduTypeCode Context triple: [GetBulk operation, pduTypeCode, GetBulkRequest-PDU]
-
A.
packetType
chosen
Indicates the specific category or kind of data packet involved in a communication or transmission.
-
B.
transmissionPowerType
Indicates the type or category of power used to transmit a signal or data between entities.
-
C.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
-
D.
labelCodeType
Indicates that one entity serves as the type or classification scheme for the labeling code applied to another entity.
-
E.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc64c2509881908fb692522d348e96 |
completed | April 1, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.