Triple

T3381839
Position Surface form Disambiguated ID Type / Status
Subject Air Berlin E71201 entity
Predicate reasonForInsolvency P13662 FINISHED
Object financial difficulties 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: financial difficulties | Statement: [Air Berlin, reasonForInsolvency, financial difficulties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForInsolvency
Context triple: [Air Berlin, reasonForInsolvency, financial difficulties]
  • A. 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.
  • B. 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.
  • C. bankruptcyType
    Indicates the specific legal category or chapter under which a bankruptcy case is filed or classified.
  • D. reasonForDisbandment chosen
    Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
  • E. reasonForDismissal
    Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
  • 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_69ad85a8fd9c819095ecedf838d2bf1b completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb5e9af608190bfb228ef99a87bb7 completed March 8, 2026, 5:46 p.m.
PD Predicate disambiguation batch_69ada434bae48190a77ea37f9274ad8f completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:14 p.m.