Triple
T14304099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairchild-Dornier |
E354644
|
entity |
| Predicate | bankruptcyDeclaredInPeriod |
P113693
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Fairchild-Dornier, bankruptcyDeclaredInPeriod, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bankruptcyDeclaredInPeriod Context triple: [Fairchild-Dornier, bankruptcyDeclaredInPeriod, early 2000s]
-
A.
bankruptcyYear
Indicates the year in which an entity was declared bankrupt or entered formal bankruptcy proceedings.
-
B.
dateOfBankruptcyFiling
Indicates the specific date on which a person or organization formally filed for bankruptcy.
-
C.
filedForBankruptcy
Indicates that an entity has formally initiated legal proceedings to declare inability to pay its debts and seek protection or reorganization under bankruptcy law.
-
D.
bankruptcyCourt
Indicates that a legal matter, case, or proceeding is handled by, filed in, or otherwise associated with a bankruptcy court.
-
E.
bankruptcyJurisdiction
Indicates the legal authority or court system that has the power to oversee and decide matters in a bankruptcy case.
- 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_69de85afabe48190926d6098047f4bcf |
completed | April 14, 2026, 6:21 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:12 a.m.