Triple
T24113507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shura Council of Bahrain |
E597441
|
entity |
| Predicate | hasInternalRegulations |
P34675
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shura Council of Bahrain, hasInternalRegulations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternalRegulations Context triple: [Shura Council of Bahrain, hasInternalRegulations, yes]
-
A.
hasRegulations
chosen
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
B.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
C.
regulatedIn
Indicates that one entity’s activity, expression, or occurrence is controlled, influenced, or modulated by another entity within a specific context or system.
-
D.
supportsRegulation
Indicates that one entity endorses, backs, or advocates for the implementation or continuation of a specific regulation.
-
E.
regulatingRules
Indicates that one entity establishes or enforces rules or standards that govern or control the behavior, operation, or conditions of another entity.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1cf75c8190ad5352d4b290e735 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:03 p.m.