Triple
T35953171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolution Trust Corporation |
E1039783
|
entity |
| Predicate | handledAssetTypes |
P184470
|
FINISHED |
| Object | real estate loans |
—
|
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: real estate loans | Statement: [Resolution Trust Corporation, handledAssetTypes, real estate loans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledAssetTypes Context triple: [Resolution Trust Corporation, handledAssetTypes, real estate loans]
-
A.
governsAssetType
Indicates that one entity has authority or control over the rules, usage, or management of a particular type or class of asset.
-
B.
hasAsset
Indicates that one entity possesses, owns, or controls another entity as an asset.
-
C.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
D.
identifiesAssetsOf
Indicates that one entity recognizes, specifies, or lists the assets that belong to or are associated with another entity.
-
E.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
- F. None of above. chosen
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_69f7b35e32d481909ef0220e6f6ff4a8 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2c66054819083897e25edb65ba7 |
completed | May 3, 2026, 8:40 p.m. |
Created at: May 3, 2026, 4:07 p.m.