Triple
T13786383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H4H |
E331267
|
entity |
| Predicate | targetAsset |
P15055
|
FINISHED |
| Object | owner-occupied homes |
—
|
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: owner-occupied homes | Statement: [H4H, targetAsset, owner-occupied homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAsset Context triple: [H4H, targetAsset, owner-occupied homes]
-
A.
assetType
chosen
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
B.
tradedAsset
Indicates that an entity is the asset or instrument being exchanged in a trade transaction between parties.
-
C.
underlyingAsset
Indicates that one asset serves as the fundamental reference or basis for the value, performance, or contractual terms of another financial instrument or derivative.
-
D.
primaryAsset
Indicates that one entity is the main or most important asset 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.
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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.