Triple
T419528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation A |
E8069
|
entity |
| Predicate | maxOfferingAmountTier2 |
P9530
|
FINISHED |
| Object | $75 million in a 12-month period |
—
|
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: $75 million in a 12-month period | Statement: [Regulation A, maxOfferingAmountTier2, $75 million in a 12-month period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxOfferingAmountTier2 Context triple: [Regulation A, maxOfferingAmountTier2, $75 million in a 12-month period]
-
A.
isSecondHighest
Indicates that one entity ranks immediately below the highest-ranked entity within a specified ordering or set.
-
B.
firstOffered
Indicates that one entity was the earliest or initial provider or proposer of something to another entity or context.
-
C.
higherTierAuthority
Indicates that one entity holds a superior or higher-ranking level of authority or control over another entity.
-
D.
setsMaximum
chosen
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
-
E.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd3b948819097d96c73d0a0f699 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.