Triple
T31119293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSMA 2000 |
E793178
|
entity |
| Predicate | post2013Regulator |
P50234
|
FINISHED |
| Object | Financial Conduct Authority |
—
|
NE NERFINISHED |
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: Financial Conduct Authority | Statement: [FSMA 2000, post2013Regulator, Financial Conduct Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: post2013Regulator Context triple: [FSMA 2000, post2013Regulator, Financial Conduct Authority]
-
A.
regulatorsInvolved
Indicates that one or more regulatory authorities are involved in overseeing, reviewing, or influencing the referenced entity or activity.
-
B.
regulatorEstablished
chosen
Indicates that an entity has formally created, instituted, or set up a regulatory body or authority.
-
C.
regulateBy
Indicates that one entity exercises control, guidance, or governance over another entity’s behavior, operation, or state through rules, mechanisms, or constraints.
-
D.
regulatorAction
Indicates an action taken by a regulatory authority toward an entity, such as enforcing rules, issuing directives, or applying sanctions.
-
E.
regulatorCovered
Indicates that an entity falls under the authority, oversight, or jurisdiction of a specified regulatory body.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:04 p.m.