Triple
T28469601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remington Arms |
E720395
|
entity |
| Predicate | hasBankruptcyFiling |
P16035
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Remington Arms, hasBankruptcyFiling, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBankruptcyFiling Context triple: [Remington Arms, hasBankruptcyFiling, 2018]
-
A.
filedForBankruptcy
chosen
Indicates that an entity has formally initiated legal proceedings to declare inability to pay its debts and seek protection or reorganization under bankruptcy law.
-
B.
hasBankruptcyMattersHandledBy
Indicates that bankruptcy-related legal or financial matters of one party are managed or handled by another party.
-
C.
dateOfBankruptcyFiling
Indicates the specific date on which a person or organization formally filed for bankruptcy.
-
D.
bankruptcy
Indicates a legal and financial state in which an entity is unable to meet its debt obligations and enters a formal process to resolve or discharge those debts.
-
E.
bankruptcyType
Indicates the specific legal category or chapter under which a bankruptcy case is filed or classified.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 2:47 a.m.