Triple
T15363273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASDAQ:SHLD |
E367342
|
entity |
| Predicate | issuerDelistingReason |
P30803
|
FINISHED |
| Object | bankruptcy of issuer |
—
|
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: bankruptcy of issuer | Statement: [NASDAQ:SHLD, issuerDelistingReason, bankruptcy of issuer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerDelistingReason Context triple: [NASDAQ:SHLD, issuerDelistingReason, bankruptcy of issuer]
-
A.
reasonForDelisting
chosen
Indicates the specific cause or justification for which an item, entity, or record has been removed from a list or registry.
-
B.
revocationReason
Indicates the reason or cause for which a previously granted status, permission, or credential has been revoked.
-
C.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
D.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
E.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e479f188190bbbc3dcd73853e02 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.