Triple
T7346243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIT Group |
E169387
|
entity |
| Predicate | wentThrough |
P6390
|
FINISHED |
| Object | Chapter 11 bankruptcy reorganization |
—
|
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: Chapter 11 bankruptcy reorganization | Statement: [CIT Group, wentThrough, Chapter 11 bankruptcy reorganization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wentThrough Context triple: [CIT Group, wentThrough, Chapter 11 bankruptcy reorganization]
-
A.
wentTo
Indicates that one entity traveled or moved from its original location to another specified place.
-
B.
underwent
chosen
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
C.
passed
Indicates that one entity successfully transferred control, responsibility, or an item (such as an object, message, or test) to another entity or through a specified stage or condition.
-
D.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
E.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
- 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.