Triple
T24407174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AV. |
E615342
|
entity |
| Predicate | isSubjectToRegulator |
P1313
|
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: [AV., isSubjectToRegulator, Financial Conduct Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubjectToRegulator Context triple: [AV., isSubjectToRegulator, Financial Conduct Authority]
-
A.
subjectToRegulation
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
-
B.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
C.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
D.
hasRegulatoryMarket
Indicates that an entity is subject to, or operates within, a specific regulatory framework or market oversight regime.
-
E.
hasRegulatedEntityType
Indicates that an entity is subject to regulation specifically because it belongs to a particular regulated category or type.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2957e8d5c8190bfed93aa308eb523 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.