Triple
T7541385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasury bonds |
E178281
|
entity |
| Predicate | investorObjective |
P77718
|
FINISHED |
| Object | capital preservation |
—
|
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: capital preservation | Statement: [Treasury bonds, investorObjective, capital preservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investorObjective Context triple: [Treasury bonds, investorObjective, capital preservation]
-
A.
fundingObjective
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
-
B.
vestmentStyle
Indicates the style or type of clothing or ceremonial garments associated with an entity.
-
C.
targetInvestorNeed
Indicates that an action, product, or communication is specifically aimed at addressing or fulfilling an investor’s particular needs or requirements.
-
D.
investmentHorizon
Indicates the typical time period over which an investment is expected to be held before its goals are evaluated or the capital is withdrawn.
-
E.
investmentScope
Indicates the range or boundaries of activities, assets, or sectors that an investment is intended or allowed to cover.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8750f80819088ddfb7a5580b5df |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5cea2748190afd607ef93e8d66c |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:48 p.m.