Triple
T8277722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specie Circular of 1836 |
E193587
|
entity |
| Predicate | prohibitsPaymentIn |
P272
|
FINISHED |
| Object | most paper banknotes |
—
|
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: most paper banknotes | Statement: [Specie Circular of 1836, prohibitsPaymentIn, most paper banknotes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitsPaymentIn Context triple: [Specie Circular of 1836, prohibitsPaymentIn, most paper banknotes]
-
A.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
B.
prohibits
chosen
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
D.
moneyBillsRestriction
Indicates a limitation or control placed on the use, amount, or handling of money bills in a given context.
-
E.
paymentNotBasedOn
Indicates that one entity’s payment or compensation is not determined, calculated, or conditioned by another specified factor, entity, or outcome.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ebb6b88190bc777b8bd72fcdbc |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.