Triple
T24657616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P U.S. Treasury Bond Index |
E610436
|
entity |
| Predicate | securityTypeIncluded |
P89715
|
FINISHED |
| Object | U.S. Treasury bills |
—
|
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: U.S. Treasury bills | Statement: [S&P U.S. Treasury Bond Index, securityTypeIncluded, U.S. Treasury bills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityTypeIncluded Context triple: [S&P U.S. Treasury Bond Index, securityTypeIncluded, U.S. Treasury bills]
-
A.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
B.
securityTypeListed
Indicates that a security is officially listed and traded on a recognized exchange or trading venue.
-
C.
securityTypeCoverage
chosen
Indicates the type or category of security that is covered or included under a given coverage or policy.
-
D.
securityTypePermitted
Indicates that a particular type or category of security is allowed or authorized within a given context or system.
-
E.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 2:34 a.m.