Triple
T5814034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn Rapid Transit Company |
E128938
|
entity |
| Predicate | causeOfReceivership |
P694
|
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: [Brooklyn Rapid Transit Company, causeOfReceivership, financial difficulties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfReceivership Context triple: [Brooklyn Rapid Transit Company, causeOfReceivership, financial difficulties]
-
A.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
B.
reasonForAssociation
Indicates that one entity is associated with another due to a specific cause, purpose, or motivating factor underlying their relationship.
-
C.
requiredIndemnityReceiver
Indicates that one party is obligated to provide indemnity (compensation or protection against loss) to another specified party.
-
D.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
E.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_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. |
Created at: March 22, 2026, 3:52 p.m.