Triple
T2504803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 144A |
E52552
|
entity |
| Predicate | transactionNature |
P40844
|
FINISHED |
| Object | private offering |
—
|
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: private offering | Statement: [Rule 144A, transactionNature, private offering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transactionNature Context triple: [Rule 144A, transactionNature, private offering]
-
A.
notableTransaction
Indicates that a transaction between entities is significant or noteworthy in context, such as being unusually large, important, or otherwise exceptional.
-
B.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
C.
transactionCount
Indicates the number of transactions that have occurred involving the specified entity or between the related entities.
-
D.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
E.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
- 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.