Triple
T5769354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Security Trust Funds |
E127288
|
entity |
| Predicate | typeOfAsset |
P15055
|
FINISHED |
| Object | book-entry government securities |
—
|
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: book-entry government securities | Statement: [Social Security Trust Funds, typeOfAsset, book-entry government securities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAsset Context triple: [Social Security Trust Funds, typeOfAsset, book-entry government securities]
-
A.
assetType
chosen
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
B.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
C.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
-
D.
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.
-
E.
primaryAsset
Indicates that one entity is the main or most important asset associated with another entity.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.