Triple
T1064489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Registration Depository |
E22978
|
entity |
| Predicate | dataSubmittedBy |
P28
|
FINISHED |
| Object | broker-dealer firms |
—
|
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: broker-dealer firms | Statement: [Central Registration Depository, dataSubmittedBy, broker-dealer firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSubmittedBy Context triple: [Central Registration Depository, dataSubmittedBy, broker-dealer firms]
-
A.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
B.
submittedTo
chosen
Indicates that one entity has formally sent or presented something (such as a document, request, or work) to another entity for consideration, review, or processing.
-
C.
dataReturned
Indicates that some data has been sent back or provided as a result of a request, query, or operation.
-
D.
draftedBy
Indicates that something (such as a document, plan, or version) was created or written in its initial form by a particular agent or author.
-
E.
dataUsers
Indicates a relationship where certain entities use, access, or consume specific data.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b90f91248190ace1534a51b82bdd |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.