Triple

T5814033
Position Surface form Disambiguated ID Type / Status
Subject Brooklyn Rapid Transit Company E128938 entity
Predicate wentIntoReceivership P67114 FINISHED
Object 1918 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: 1918 | Statement: [Brooklyn Rapid Transit Company, wentIntoReceivership, 1918]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wentIntoReceivership
Context triple: [Brooklyn Rapid Transit Company, wentIntoReceivership, 1918]
  • A. 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.
  • B. emergedFromBankruptcy
    Indicates that an entity has successfully completed bankruptcy proceedings and returned to normal financial or operational status.
  • C. 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.
  • D. bankruptcyCourt
    Indicates that a legal matter, case, or proceeding is handled by, filed in, or otherwise associated with a bankruptcy court.
  • E. bankruptcyType
    Indicates the specific legal category or chapter under which a bankruptcy case is filed or classified.
  • 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_69c0084788848190bcf71f6bc5d71597 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0400f1af881908d376ea4793f6dea completed March 22, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69c0333fdd7081908d829265caa2ac11 completed March 22, 2026, 6:21 p.m.
PDg Predicate description generation batch_69c0400dbec08190b2ef73689b2c0c31 completed March 22, 2026, 7:16 p.m.
Created at: March 22, 2026, 3:52 p.m.