Triple
T2798172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reg A |
E53087
|
entity |
| Predicate | offeringDocumentName |
P19006
|
FINISHED |
| Object | Form 1‑A |
—
|
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: Form 1‑A | Statement: [Reg A, offeringDocumentName, Form 1‑A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeringDocumentName Context triple: [Reg A, offeringDocumentName, Form 1‑A]
-
A.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
B.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
C.
documentationType
chosen
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
D.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
E.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddf204148190a53f3f30d645d94c |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.