Triple
T1975749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SETS |
E42906
|
entity |
| Predicate | regulatesAccessFor |
P15393
|
FINISHED |
| Object | member firms of the London Stock Exchange |
—
|
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: member firms of the London Stock Exchange | Statement: [SETS, regulatesAccessFor, member firms of the London Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesAccessFor Context triple: [SETS, regulatesAccessFor, member firms of the London Stock Exchange]
-
A.
controlsAccessTo
chosen
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
B.
regulatesWith
Indicates that one entity controls, modulates, or influences the activity, state, or behavior of another entity through some regulatory mechanism or interaction.
-
C.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
E.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f835108190b0709ccf3a487a96 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.