Triple
T35953219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolution Funding Corporation |
E1039784
|
entity |
| Predicate | relatedToAgency |
P102203
|
FINISHED |
| Object | Resolution Trust Corporation |
E319790
|
NE 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: Resolution Trust Corporation | Statement: [Resolution Funding Corporation, relatedToAgency, Resolution Trust Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToAgency Context triple: [Resolution Funding Corporation, relatedToAgency, Resolution Trust Corporation]
-
A.
relevantAgency
chosen
Indicates that an agency has authority, responsibility, or significant involvement in relation to a particular matter, entity, or action.
-
B.
belongsToAgency
Indicates that an entity is under the authority, control, or affiliation of a specific agency.
-
C.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
relatedDelegate
Indicates that one entity serves as a delegate, proxy, or representative that is functionally related or linked to another entity.
- F. None of above.
Provenance (4 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cb8241308190b1c5ea7f7ff71cef |
completed | June 22, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.