Triple
T7541368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasury bonds |
E178281
|
entity |
| Predicate | priceMoves |
P15880
|
FINISHED |
| Object | inversely with yields |
—
|
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: inversely with yields | Statement: [Treasury bonds, priceMoves, inversely with yields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceMoves Context triple: [Treasury bonds, priceMoves, inversely with yields]
-
A.
priceMoveConvention
Indicates how price changes are expressed or measured for a financial instrument (e.g., in absolute terms, ticks, or percentage moves).
-
B.
relativePrice
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
C.
priceInfluencedBy
chosen
Indicates that the price of one entity is affected or determined by another specified factor or entity.
-
D.
positionChange
Indicates a change in an entity’s spatial or positional state from one location or configuration to another.
-
E.
priceRelationship
Indicates a comparative relationship between the prices of two entities, such as one being higher, lower, or equal to the other.
- 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_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. |
Created at: March 27, 2026, 3:48 p.m.