Triple
T2504806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 144A |
E52552
|
entity |
| Predicate | requiresPurchaserStatus |
P40845
|
FINISHED |
| Object | qualified institutional buyer |
—
|
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: qualified institutional buyer | Statement: [Rule 144A, requiresPurchaserStatus, qualified institutional buyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPurchaserStatus Context triple: [Rule 144A, requiresPurchaserStatus, qualified institutional buyer]
-
A.
hasInAppPurchases
Indicates that an application offers additional content, features, or services that users can buy from within the app itself.
-
B.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
C.
requiresSubscription
Indicates that access to or use of something is conditional on having an active subscription.
-
D.
requiresCheckOut
Indicates that one entity must be formally checked out or borrowed before it can be used, accessed, or taken by another entity.
-
E.
requiredPledgeFrom
Indicates that one entity mandates or demands a pledge or commitment from another entity as a prerequisite or condition.
- F. None of above. chosen
Provenance (4 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd65c9d508190957285a078698ed2 |
completed | March 7, 2026, 7:40 a.m. |
Created at: March 6, 2026, 9:46 p.m.