Triple
T2155950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldrich–Vreeland Act |
E47886
|
entity |
| Predicate | allowedCollateral |
P273
|
FINISHED |
| Object | corporate bonds |
—
|
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: corporate bonds | Statement: [Aldrich–Vreeland Act, allowedCollateral, corporate bonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedCollateral Context triple: [Aldrich–Vreeland Act, allowedCollateral, corporate bonds]
-
A.
collateralRequired
Indicates that a party must provide collateral as a condition or security for an obligation, transaction, or agreement.
-
B.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
C.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
D.
alsoHolds
Indicates that a condition, property, or relation that applies in one context or case simultaneously applies in another context or case.
-
E.
allowedTransport
Indicates that a particular mode or means of transport is permitted for use between the related entities.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe669c188190bb4c1c391ca848b0 |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.