Triple
T24276284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silicon Valley Bank |
E605418
|
entity |
| Predicate | regulatoryStatusAfterCollapse |
P121935
|
FINISHED |
| Object | receivership |
—
|
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: receivership | Statement: [Silicon Valley Bank, regulatoryStatusAfterCollapse, receivership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryStatusAfterCollapse Context triple: [Silicon Valley Bank, regulatoryStatusAfterCollapse, receivership]
-
A.
regulationStatus
Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
-
B.
regulatedStatusOf
Indicates that one entity has regulatory authority or control over the status or condition of another entity.
-
C.
legalStatusAfterEvent
chosen
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
-
D.
regulatoryOutcome
Indicates the result or consequence of a regulatory process, such as approval, rejection, modification, or other formal decision made by a regulatory authority regarding an entity or action.
-
E.
legalStatusAfterEndTime
Indicates the legal status or condition that applies to an entity after a specified end time has passed.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5fd03481908e502c6944d7fe69 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.