Triple
T8508060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetBulkRequest-PDU |
E201383
|
entity |
| Predicate | variableBindingsContain |
P19434
|
FINISHED |
| Object | list of VarBind structures |
—
|
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: list of VarBind structures | Statement: [GetBulkRequest-PDU, variableBindingsContain, list of VarBind structures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variableBindingsContain Context triple: [GetBulkRequest-PDU, variableBindingsContain, list of VarBind structures]
-
A.
hasVariable
Indicates that one entity includes, defines, or is associated with a particular variable.
-
B.
bindsTo
Indicates that one entity physically or functionally attaches or connects to another, often with some specificity or selectivity in the interaction.
-
C.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
D.
variableCondition
Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
-
E.
V_1Contains
chosen
Indicates that one entity holds, encloses, or has within it another entity as a part or subset.
- 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_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. |
Created at: March 30, 2026, 6:15 p.m.