Triple
T5028159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC2 |
E113227
|
entity |
| Predicate | exportControlContext |
P13403
|
FINISHED |
| Object | designed to comply with U.S. export restrictions |
—
|
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: designed to comply with U.S. export restrictions | Statement: [RC2, exportControlContext, designed to comply with U.S. export restrictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportControlContext Context triple: [RC2, exportControlContext, designed to comply with U.S. export restrictions]
-
A.
exportControl
chosen
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
B.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
C.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
D.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
E.
transferredControlFrom
Indicates that authority or control over something has been moved or handed over from one entity to another.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738d852c8190a122354f1e1f5343 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.