Triple
T35953223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolution Funding Corporation |
E1039784
|
entity |
| Predicate | hasLiabilitiesType |
P75181
|
FINISHED |
| Object | long-term bonds |
—
|
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: long-term bonds | Statement: [Resolution Funding Corporation, hasLiabilitiesType, long-term bonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiabilitiesType Context triple: [Resolution Funding Corporation, hasLiabilitiesType, long-term bonds]
-
A.
liabilityType
chosen
Indicates the specific category or nature of liability associated with an entity, obligation, or financial exposure.
-
B.
hasMainCreditorType
Indicates the primary category or type of creditor that holds the main claim or financial interest in relation to an entity.
-
C.
liabilitiesAtBankruptcy
Indicates the total obligations or debts an entity has outstanding at the time it is declared bankrupt.
-
D.
hasOngoingObligations
Indicates that an entity is currently bound by duties or responsibilities that are still in effect and not yet fulfilled or terminated.
-
E.
hasTypeOfCredit
Indicates that an entity is associated with or characterized by a specific type or category of credit.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 3, 2026, 4:07 p.m.