Triple
T22192119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultra U.S. Treasury bond |
E548451
|
entity |
| Predicate | parValue |
P7345
|
FINISHED |
| Object | typically 100 or 1000 USD in quotation terms |
—
|
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: typically 100 or 1000 USD in quotation terms | Statement: [Ultra U.S. Treasury bond, parValue, typically 100 or 1000 USD in quotation terms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parValue Context triple: [Ultra U.S. Treasury bond, parValue, typically 100 or 1000 USD in quotation terms]
-
A.
primaryValue
Indicates the main or most significant value associated with an entity, attribute, or measurement within a given context.
-
B.
value
chosen
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
C.
par
Indicates that two entities are parallel to each other in space or direction.
-
D.
valueParity
Indicates that two compared values share the same parity (both even or both odd), or more generally, how a value’s parity is characterized in a given context.
-
E.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae49ec881908fa42446b19e3f2d |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.