Triple
T2231044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherman Silver Purchase Act of 1890 |
E48764
|
entity |
| Predicate | requiredPurchaseFrequency |
P8512
|
FINISHED |
| Object | monthly |
—
|
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: monthly | Statement: [Sherman Silver Purchase Act of 1890, requiredPurchaseFrequency, monthly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredPurchaseFrequency Context triple: [Sherman Silver Purchase Act of 1890, requiredPurchaseFrequency, monthly]
-
A.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
B.
frequencyRequirement
chosen
Indicates a constraint specifying how often an action, event, or condition must occur within a given context or time frame.
-
C.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
D.
requiresSubscription
Indicates that access to or use of something is conditional on having an active subscription.
-
E.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc06b7374819089fe643e12797bfd |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.