Triple
T8508039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetBulkRequest-PDU |
E201383
|
entity |
| Predicate | responsePDUType |
P82888
|
FINISHED |
| Object | GetResponse-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: GetResponse-PDU | Statement: [GetBulkRequest-PDU, responsePDUType, GetResponse-PDU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responsePDUType Context triple: [GetBulkRequest-PDU, responsePDUType, GetResponse-PDU]
-
A.
responseField
Indicates that a particular piece of information is included as part of a response or output structure.
-
B.
responseTermination
Indicates that a response, process, or interaction has been brought to an end, either normally or due to some terminating condition.
-
C.
UNResponse
Indicates that an entity issues, represents, or embodies an official response, action, or position taken by the United Nations regarding another entity or situation.
-
D.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
E.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
- F. None of above. chosen
Provenance (4 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5de18448190a695eec609b34e1a |
completed | March 31, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:14 p.m.