Triple
T1064534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trade Reporting and Compliance Engine |
E22979
|
entity |
| Predicate | reportingRequirement |
P12768
|
FINISHED |
| Object | FINRA member 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: FINRA member firms | Statement: [Trade Reporting and Compliance Engine, reportingRequirement, FINRA member firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportingRequirement Context triple: [Trade Reporting and Compliance Engine, reportingRequirement, FINRA member firms]
-
A.
requiresReportTo
chosen
Indicates that one entity is obligated to submit or provide a report to another entity.
-
B.
requiresReportFrom
Indicates that one entity is obligated to obtain or receive a report from another entity.
-
C.
reportType
Indicates the specific category or kind of report associated with an entity or action.
-
D.
dialogRequirement
Indicates that a certain condition, piece of information, or interaction must occur within a dialog or conversation for a related action, state, or process to proceed or be considered valid.
-
E.
publicationRequirement
Indicates that an entity must be publicly disclosed or published as a condition for validity, compliance, or progression in a process.
- 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.