Triple
T1064535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trade Reporting and Compliance Engine |
E22979
|
entity |
| Predicate | reportingScope |
P14568
|
FINISHED |
| Object | secondary market transactions in eligible fixed-income securities |
—
|
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: secondary market transactions in eligible fixed-income securities | Statement: [Trade Reporting and Compliance Engine, reportingScope, secondary market transactions in eligible fixed-income securities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportingScope Context triple: [Trade Reporting and Compliance Engine, reportingScope, secondary market transactions in eligible fixed-income securities]
-
A.
coverageScope
chosen
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
B.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
-
C.
standardizationScope
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
-
D.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
E.
identificationScope
Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
- 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.