Triple
T14298185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapter 11 – Reorganization |
E354493
|
entity |
| Predicate | createsStatus |
P113666
|
FINISHED |
| Object | debtor in possession |
—
|
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: debtor in possession | Statement: [Chapter 11 – Reorganization, createsStatus, debtor in possession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsStatus Context triple: [Chapter 11 – Reorganization, createsStatus, debtor in possession]
-
A.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
B.
statusOfFirstCreation
Indicates the condition or state associated with an entity’s initial act of creation or first-time establishment.
-
C.
customStatus
Indicates that an entity has a user-defined or non-standard status assigned to it.
-
D.
statusOfMostRecentCreation
Indicates the current state or condition of the most recently created item or entity in a given context.
-
E.
classifiedStatusAtCreation
Indicates that an entity’s classification level or status (e.g., security or confidentiality classification) at the time it was created is being specified.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717cfc948190ace5f1c91283b1c3 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.