Triple
T646082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston and Maine Railroad |
E11243
|
entity |
| Predicate | enteredBankruptcy |
P10968
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [Boston and Maine Railroad, enteredBankruptcy, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredBankruptcy Context triple: [Boston and Maine Railroad, enteredBankruptcy, 1970]
-
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.
dateOfBankruptcyFiling
chosen
Indicates the specific date on which a person or organization formally filed for bankruptcy.
-
C.
enteredIntoForce
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
-
D.
enteredIntoForceBy
Indicates that a legal instrument, agreement, or provision became legally effective as a result of an action taken by a specified authority, event, or instrument.
-
E.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f1b24b08190897d8aedb877bd83 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0c0dcc8190849211d45489a5a7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.