Triple
T17923528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reg NMS |
E448132
|
entity |
| Predicate | subPennyRuleThreshold |
P14326
|
FINISHED |
| Object | $1.00 |
—
|
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: $1.00 | Statement: [Reg NMS, subPennyRuleThreshold, $1.00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subPennyRuleThreshold Context triple: [Reg NMS, subPennyRuleThreshold, $1.00]
-
A.
minimumPayoutThreshold
Indicates the lowest payout amount or value that must be reached before a payment or disbursement is triggered.
-
B.
thresholdFor
chosen
Indicates that one entity specifies the minimum or limiting value at which a condition, effect, or state involving another entity begins to occur or change.
-
C.
currencyOfThreshold
Indicates the specific currency in which a given threshold value is defined or measured.
-
D.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
E.
penaltyRules
Indicates the rules or conditions under which penalties are defined, applied, or enforced in a given context.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30bde508190bc529ccae81f0e2a |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.