Triple
T26954146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCorp Bank |
E678850
|
entity |
| Predicate | operationalStatusAfterCollapse |
P126340
|
FINISHED |
| Object | liquidated |
—
|
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: liquidated | Statement: [MCorp Bank, operationalStatusAfterCollapse, liquidated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStatusAfterCollapse Context triple: [MCorp Bank, operationalStatusAfterCollapse, liquidated]
-
A.
operationalStatusAtEnd
Indicates the final operational condition or state of an entity at the conclusion of a specified period or process.
-
B.
consequenceOfCollapse
chosen
Indicates that one event, state, or condition occurs as a direct result of a collapse.
-
C.
statusAfterRescue
Indicates the condition or state an entity is in following a rescue event or operation.
-
D.
coreCollapseStatus
Indicates the current state or outcome of a system’s core undergoing gravitational collapse.
-
E.
statusOfCityAfterEvent
Indicates the condition or state a city is in as a result of a specific 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 27, 2026, 6:26 a.m.