Triple
T2238743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbott Laboratories |
E49343
|
entity |
| Predicate | regulatoryFiling |
P14003
|
FINISHED |
| Object | SEC 10-K |
—
|
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: SEC 10-K | Statement: [Abbott Laboratories, regulatoryFiling, SEC 10-K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryFiling Context triple: [Abbott Laboratories, regulatoryFiling, SEC 10-K]
-
A.
regulatoryDocument
Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
-
B.
filingForm
chosen
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
-
C.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
D.
hasSECFilingsURL
Indicates that there is a URL linking an entity to its filings or disclosure documents submitted to the U.S. Securities and Exchange Commission (SEC).
-
E.
filingMethod
Indicates how a document, record, or information is submitted or recorded, such as the process, channel, or format used for filing.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0bb3fac81908b1e8518951dd160 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.