Triple
T11468296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 144 |
E271832
|
entity |
| Predicate | safeHarborStatus |
P99448
|
FINISHED |
| Object | non-exclusive |
—
|
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-exclusive | Statement: [Rule 144, safeHarborStatus, non-exclusive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safeHarborStatus Context triple: [Rule 144, safeHarborStatus, non-exclusive]
-
A.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
-
B.
sanctioningStatus
Indicates the current status of formal penalties, restrictions, or sanctions applied to an entity by an authority.
-
C.
guaranteeStatus
Indicates the current state or condition of a guarantee associated with an entity or agreement.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
E.
regulationStatus
Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d82949e3688190b024a4980666c94f |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:35 p.m.