Triple
T3384262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASML |
E71257
|
entity |
| Predicate | regulatorySensitivity |
P34837
|
FINISHED |
| Object | Subject to export control regulations |
—
|
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: Subject to export control regulations | Statement: [ASML, regulatorySensitivity, Subject to export control regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatorySensitivity Context triple: [ASML, regulatorySensitivity, Subject to export control regulations]
-
A.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
B.
subjectToRegulation
chosen
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
-
C.
regulationImpact
Indicates how a regulation influences, constrains, or alters the behavior, performance, or outcomes associated with the related entities.
-
D.
regulatoryResponse
Indicates a reaction, decision, or adjustment made by a regulatory body in response to a particular event, condition, or entity’s behavior.
-
E.
regulatoryAudience
Indicates that something is intended for, directed toward, or relevant to a regulatory body or oversight authority as its audience.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ec85d08190b28110157c39435f |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.