Triple
T7461157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series EE savings bond |
E176250
|
entity |
| Predicate | canBeUsedAsCollateral |
P55948
|
FINISHED |
| Object | no, in general |
—
|
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: no, in general | Statement: [Series EE savings bond, canBeUsedAsCollateral, no, in general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedAsCollateral Context triple: [Series EE savings bond, canBeUsedAsCollateral, no, in general]
-
A.
collateralType
chosen
Indicates the kind or category of collateral associated with an obligation, agreement, or financial exposure.
-
B.
canBeSeizedBy
Indicates that one entity is legally or physically able to be taken control of, captured, or confiscated by another entity.
-
C.
collateralRequired
Indicates that a party must provide collateral as a condition or security for an obligation, transaction, or agreement.
-
D.
isBorrowerOwned
Indicates that an entity is owned or controlled by its borrowers or customers, rather than by external shareholders or private owners.
-
E.
hasLendingInstrument
Indicates that an entity possesses or utilizes a specific financial instrument used for lending.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d6cf8c8190a31cac121d151d78 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.