Triple
T8508028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetBulkRequest-PDU |
E201383
|
entity |
| Predicate | parameterControls |
P73966
|
FINISHED |
| Object | non-repeaters |
—
|
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: non-repeaters | Statement: [GetBulkRequest-PDU, parameterControls, non-repeaters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterControls Context triple: [GetBulkRequest-PDU, parameterControls, non-repeaters]
-
A.
settingControlled
chosen
Indicates that one entity regulates, adjusts, or determines the configuration or parameters of another entity.
-
B.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
C.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
D.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
E.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
- 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:14 p.m.