Triple
T31600915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian Treasury bonds |
E806345
|
entity |
| Predicate | areSoldTo |
P47118
|
FINISHED |
| Object | individual investors |
—
|
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: individual investors | Statement: [Brazilian Treasury bonds, areSoldTo, individual investors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areSoldTo Context triple: [Brazilian Treasury bonds, areSoldTo, individual investors]
-
A.
shipSoldTo
Indicates that a ship has been sold by one party and transferred in ownership to another specified party.
-
B.
areSoldThrough
Indicates that items or services are made available to buyers via a particular sales channel, intermediary, or distribution method.
-
C.
plansSoldBy
Indicates that one entity is the seller or provider of plans that are purchased or obtained by another entity.
-
D.
someAssetsSoldTo
chosen
Indicates that a subset of an entity’s assets has been transferred in ownership to another party through a sale.
-
E.
soldDueTo
Indicates that one entity was sold as a consequence of, or motivated by, another specified factor, event, or condition.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:32 p.m.